-
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 Communicate With Customers During Uncertain Times | Salesforce Guide
How do you communicate with your customers when they’re facing uncertainty? How do you move beyond basic customer transactions and create memorable, human moments? Is…
5 Top Benefits of Using Salesforce CRM for Banks in 2023
A CEO of a well-known investment bank once remarked proper use of technology is the cornerstone of success of a modern financial organization, and rightly…
Salesforce Summer '22 Release Features
Salesforce is back with its Summer ‘22 release notes. Salesforce releases updates on a regular basis to enhance the productivity, consistency, reliability, and availability of…
Popular Salesforce Videos
Getting started with salesforce
Salesforce is a customer relationship management solution that brings companies and customers together. It's one integrated CRM platform that gives all your departments — including…
Successfully Retrieving Metadata From Salesforce org Using Packages
In this session, we will uncover various strategies that developers can use to pull metadata from Salesforce org successfully. Watch this video and learn everything.…
Salesforce Standard vs Custom Objects Explained
Salesforce, a leading customer relationship management (CRM) platform, offers both custom and standard objects to organize and manage data effectively. Standard objects are pre-built components…
