-
Why we use sObject in code instead of an object?
Why we use sObject in code instead of an object, i.e Account,Contact or any custom object? Can anybody explain something about it?
-
1 Reply
-
Hi Gourav,
sObject is a generic abstract type that corresponds to any persisted object type. The generic sObject can be cast into a specific sObject type and object can be of JSON object. While JSON parsing, after parsing I got object which is of JSON object type. I am referencing that JSON object with object.
Thanks
Log In to reply.
Popular Salesforce Blogs
Key Management in Shield Platform Encryption | Salesforce Security Guide
Shield Platform Encryption licenses Salesforce head to deal with the life cycle of their information encryption keys while shielding those keys from unapproved access. To…
How to Create a Seamless Customer Experience with Salesforce Experience Cloud?
Business success is closely tied to excellent customer experience. This is not new, but in the era of heightened expectations and instant gratification, companies feel…
Manufacturing Salesforce Cloud | Boost your production with better predictions
Manufacturers are the most valuable assets for any company’s growth because they mold the products into what they are, and the products are the reason…
Popular Salesforce Videos
Salesforce: Advanced 'Change Owner' Control in Flow and Apex
Alex Edelstein explains the Salesforce feature known as the 'Change Owner' Control in Flow and Apex. This video is geared toward those already familiar with…
Salesforce Consulting - WHAT YOU NEED TO KNOW
If you're already working as a Salesforce Professional or you're interested in where your Salesforce Career will take you this is for you. This explains…
How Much I Earn as a Salesforce Consultant!
In this video, Adam Foyston gives a detailed look at the earnings of Salesforce consultants, how they compare to the earnings of Salesforce admins, and…
