BigObjects let you store and manage very large amounts of data on the Salesforce platform. You can use a BigObject to store very high volumes of customer event history such as weblog data, loyalty data, customer event history or archive data. You create BigObjects by using the Metadata API, and then you can see them in the Setup UI. BigObjects use the suffix __b and because they have their own key prefix range they don’t affect other object limits. You can insert and query data via the Bulk API, SOAP API, and Data Pipelines.

BigObjects support the following fields:

• DateTime

• Lookup

• Text

You can create a Lookup field on a BigObject referring to a standard or custom object so that you can write JOIN queries. You can create Wave data sets with BigObjects using Data Pipelines.

The Field Audit Trail feature, based on BigObjects, lets you define a policy to retain archived field history data up to 10 years, independent of field history tracking.

Use Cases:

• Data archiving—If you have a large amount of data stored in standard or custom objects in Salesforce, use BigObjects to store
historical data.
• Compliance—Retain records on Salesforce for long periods of time to comply with regulatory requirements.
• Analytics—Perform sophisticated analysis on historical data, including correlating it with live data in Salesforce.
• Customer Loyalty—Store and analyze customer data to refine the customer relationship.


• Once you define a BigObject’s metadata, you can add fields but you can’t change or remove fields.
• You can’t change data in a BigObject, but you can make a copy with different data.
• Because data in a BigObject never changes, there is no field history and you can’t use triggers.
• BigObjects don’t support sharing rules. You can use permission sets and field-level security to control who can view BigObjects and
who has create and read permissions.
• You can’t define a BigObject from a sandbox and deploy to a production environment. BigObjects don’t have an In Development
• List Views aren’t supported for BigObjects.
• Permissions on BigObjects are restrictive by default. You must explicitly grant permissions using permission sets or profiles so that
users can create and view BigObjects.
• The only SOQL relationship queries available are based on a lookup field from a BigObject to a standard or custom object.
• You can’t insert into BigObjects via Apex.

Bigobjects implementation guide, Please click here



Leave a Comment

Your email address will not be published. Required fields are marked *

Select Language »