-
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
How to Hire the Best Commerce Cloud Consultant
Your online store needs more than just good products. It needs the right platform, the right strategy, and the right person to bring it all…
Export and Import Functionalities in Salesforce | All You Need to Know
To move attachment data from one Salesforce org to another, from one object to another, or to import from one place, you must follow two…
Salesforce Org Migration to Hyperforce
What is Org Migration? In order to arrange for our customers' continuing growth, we have a tendency to sometimes ought to perform associate degree activity…
Popular Salesforce Videos
Salesforce Spring 22 Treasure Hunt for Flow | Migrate your Workflow Rules to Flows
Salesforce Spring 22 Treasure Hunt for Flow 0:00 Register for pre-release org 0:27 Flow Trigger Explorer 2:07 Auto-Layout and Freeform option as Picklist 3:00 Set…
Guide to Salesforce Manufacturing Cloud | Beginners
Unlock the Power of Salesforce Manufacturing Cloud | Streamline Your Manufacturing Operations In this video, we dive deep into Salesforce Manufacturing Cloud and explore how…
How To Create A Case Assignment Rule In Salesforce
Learn all about how to create Case Assignment rules. In this video, the following points will be covered - 1. Introduction To Case Assignment Rule…
