What are Salesforce Big Objects? | The Developer Guide

What are Salesforce Big Objects? | The Developer Guide

We are all aware that Salesforce objects are used to manage and tinker with our data. Standard objects, custom objects, and external objects are likely all familiar to you. However, you'll want to use Salesforce Big Objects if you need to manage a large volume of data. These objects maintain performance while managing billions of data records. For a comprehensive perspective of your consumers, Salesforce Big Objects let you import sizable datasets from external systems into a big object. The fact that Big Objects do not count toward the data storage limit is its main advantage. 

A common set of APIs can be used by clients and external systems to access Big Objects' data. Both Salesforce Classic and Big Objects are accessible. 

Types of Salesforce Big Objects 

There are 2 types of Big Objects: 

  1. The Standard Big Object: They are defined by Salesforce. They include Field, History, and Archive and are part of the Field Audit Trail product. This is helpful for organizations that have a use case for regulations on auditing and data retention. 
  2. The Custom Big Objects: They are defined by the user as per their requirement.  

dont miss out iconDon't forget to check out: Begin With Big Objects in Salesforce | The Developer Guide

Considerations for using Salesforce Big Objects  

  1. Big objects only support object and field permission. So you can implement sharing based rules on this. 
  2. You can’t use standard features of Salesforce like triggers, flows, processes on Big Objects. 
  3. You can create up to 100 big objects per org. The limit of the number of fields on the big object is similar to the custom object and it depends on your org’s edition and licensing. 
  4. You can create big objects and fields from the UI as well as using Metadata API. 
  5. Big objects available in Enterprise, Performance, Unlimited, and Developer Editions with one million records limit but by using an add-on license we can increase record capacity and Async SOQL. 
  6. Suffix for the big objects is __b. 
  7. Big Objects support custom Salesforce Lightning and Visualforce components instead of standard UI elements like detail pages, list views, and so on. 
  8. Big objects only support Lookup Relationship, Date, Time, Email, Number, Phone, Text, Long Text Area, and URL Field types.  
  9. Big objects do not support encryption. 

Considerations When Using Big Objects 

  1. Use Setup or the Metadata API to define a big object or add a field to a unique big object. 
  2. Instead of traditional UI elements like home pages, detail pages, list views, and so forth, big objects support bespoke Lightning and Visualforce components. 
  3. Per organisation, 100 huge objects can be created. Similar to the limits on custom objects, the limits for huge object fields vary depending on the licence level for your organisation. 
  4. Accessing large items in another org using Salesforce Connect external objects is not possible. 
  5. Encryption is not supported for large objects. Data that has been encrypted and archived from a standard or custom object is kept on the big object in clear text. 

dont miss out iconCheck out another amazing blog by Pranjal: All You Need to Know to Make a Scratch Org and Your Domain


Popular Salesforce Blogs