-
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
Integrate Salesforce with MuleSoft
In this blog we are focusing on Salesforce integration with MuleSoft. Firstly, we will need a Salesforce developer account by clicking on the following link:…
Sender Authentication Package (SAP) in Marketing Cloud: How to Use It to Improve Brand Awareness
To increase the chances of your emails reaching their intended recipients, they should be authenticated, not just validated. Authentication is serious to Google and other…
Integrations in Salesforce | All You Need to Know
So, let’s study integration in Salesforce! Why do we need Integration? So, we need integration when we want to connect two or more systems together. For…
Popular Salesforce Videos
Salesforce Integration Cloud - Connect Devices, Data and Customers
Salesforce Integration Cloud incorporates an arrangement of services and tools that make it simple for clients to surface their information paying little attention to where…
Custom Types in Lightning-datatable | Interchange | Salesforce Tutorial
First episode of our new Interchange series, in which we will deep dive in how to define custom types for a lightning-datatable component. Concretely, we’ll…
Salesforce Nonprofit Cloud Explained
Discover how Salesforce Nonprofit Cloud helps organizations drive social change through better donor management, volunteer coordination, and streamlined operations. In this video, we'll explore the…
