function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
davcondevdavcondev 

Maximum Custom BigObjects Rows usage-based entitlement = 1m

In our production org there is a usage-based entitlement entry of "Maximum Custom BigObjects Rows" with value of 1 million. Is this a hard limit on the number of records?

If so, setting the record limit so low nullifies much of the potential utility of BigObjects. The point at which BigObjects become valuable is 1 million records and above i.e. the point at which SObjects would experience performance degradation.

(Posting in developer forums because most aspects of BigObjects management aren't available yet in configuration.)