-
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
Mastering Salesforce Packages: Managed vs. Unmanaged
Salesforce packages simplify application development, deployment, and distribution in the Salesforce ecosystem. This blog explores Salesforce packages, their significance for administrators, developers, and users. We'll…
FlexDeploy Loves Salesforce: Deploy Salesforce Apps and Metadata Objects
As you likely know by now, FlexDeploy is an Enterprise DevOps platform with fully integrated support for Salesforce apps, metadata customizations, integrations and more. This…
How to Get Current Record Id in Lightning Web Component | Salesforce Developer Guide
Getting record in Lightning Aura Component is quite easy, we use force:hasRecordId and get the result in controller by using, getRecordId:function(component,event, helper){ var currentRecordId…
Popular Salesforce Videos
How Can Salesforce Help To Transform Business Into A Sales Powerhouse?
This video will help you understand what is Salesforce and how it can help transform businesses. Salesforce CRM will help to transform your organization to…
Proven Platform Development with DevOps & Agile on Salesforce
Digital business demands and user expectations have raised the bar on how CRM solutions are utilized in the enterprise. Technical professionals developing solutions with Salesforce…
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…
