In Salesforce, We already know about Standard objects, Custom objects, and External Object. These objects assist you to handle and operate data. But if we have a large amount of data then it’s difficult to effectively handle them. That’s the reason Big Objects come in.
So, Let’s discuss a big object...
A big object manages and stores large amounts of data on the Salesforce. We can store data from the different objects or bring huge datasets from outside frameworks into a big object to get a full perspective on your clients. Customers and external frameworks use a standard set of APIs to get data from big objects. A big object is the Non-transactional and Horizontally scalable distributed database.
A big object gives a reliable accomplishment, regardless of whether you have 1 million records, or 1 billion. It means a Big object can handle large amounts of data within Salesforce without affecting performance.
Don't forget to check out: The Complete Guide to Controllers in Salesforce
Let’s Discuss The Types of Big Objects Available in Salesforce
- Standard Big Object: It is described by Salesforce and remembered for the Salesforce products. Example: FieldHistoryArchieve is a standard big object that handles data of Field Audit Trail products. FieldHistoryArchieve permits you to manage up to 10 years of archive field history information. We can not customize the Standard big object.
- Custom Big Object: It extends the functionality that the Salesforce platform gives. We can create custom big objects in Setup to store data in Salesforce and here we can set its definition, fields, and records. We can also define this object with the metadata API.
Follow These Steps To Create a Custom Big Object:
- Go to Setup → Enter Big object in Quick Find Box → Select Big Objects → Click on the New button.
- Enter the Big Object information (label, object name, etc), add custom fields, and index.
- Click on the Save button and change status to deployed.
Let’s Discuss Use Cases of Big Object:
- 360° View of the Customer: We have a lot of client data we need to store. Extend your Salesforce information model to incorporate p8oint by point data from devotion programs, feeds, clicks, billing, and provisioning data, and that's just the beginning.
- Auditing and Tracking: It tracks and keeps a long term perspective of users’ Salesforce usage for analysis or compliance purposes.
- Historical Archive
- Querying Big Objects: We can run queries on big objects by using SOQLor with async SOQL.
Check out another amazing blog by Shweta here: Salesforce Lightning:map - Show Locations on Google Map
Important Point of Big Object:
- Big Object only stands for the object and field permissions.
- When you have deployed a big object, you can not edit and delete the list (index). But if you want to change the index, you have to create a new big object.
- You can make up to 100 major articles for each Salesforce organization. The limits for big object fields are like the limits on custom objects and rely upon your organization's permit type.
- Big objects don’t uphold exchanges that incorporate big objects, standard objects, and custom objects.
- To help the size of information in a big object, you can't utilize triggers, flows, processes, and the Salesforce application.