-
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
Trends to watch in Cloud Computing – 2017
Over the past few years, ease of access and enhanced security features has made cloud to attain great popularity. As a result of which, today,…
Implementing WebMerge for Salesforce Using Apex
Webmerge is used to Customize and Automate Your Document Generation. It is an online service that self-operating your document creation process. It helps to create…
Why Businesses Struggle to Choose Between Salesforce and Odoo (And How to Decide)
Choosing the right business platform is not always as simple as comparing features and prices. For many growing companies, the decision comes down to two…
Popular Salesforce Videos
Salesforce Mobile Publisher Demo
With Salesforce Mobile Publisher, you can create pixel-perfect mobile applications for employees, customers, and partners. Check out this video and learn all you need to…
Salesforce Loves Small Business
Running a small business takes a lot of heart during even the best of times. 2020 has presented a series of challenges that have hit…
Salesforce Lightning Design System (SLDS) and Components
The Salesforce Lightning Design System (SLDS) helps you build applications with the look and feel of Lightning Experience without writing a single line of CSS.…
