-
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
Build Your First Blockchain with Salesforce Apex
Introduction of Blockchain According to Wikipedia "A blockchain, originally blockchain is a growing list of records, called blocks, which are linked using cryptography." Blockchain was…
Dynamic Sharing of Standard & Custom Objects through Salesforce Apex
Apex Sharing is sharing record access through a program using Salesforce Apex through which can grant access to users or groups of users. We can use…
Your Salesforce Implementation Guide
Early-stage startups, mid-sized companies, large enterprises — no matter your size, you can only ignore the importance of implementing a Salesforce solution for so long.…
Popular Salesforce Videos
Salesforce and Slack: Success from Anywhere - Your Digital HQ
Welcome to Success from Anywhere: Your Digital HQ. Join our Slack-First Customer 360 event to find out more. Register now: https://www.salesforce.com/events-master/digital-hq/ Success Anywhere means coming…
Similarity and Difference Between SFRA and PWA | Which One to Choose? | Salesforce
Choosing SFCC as the platform necessitates a major decision: on what architecture will your channels be based? When learning about Salesforce B2C Commerce Cloud, you'll…
Integrating System with Salesforce Commerce Cloud
Designed for retail as well as eCommerce, Salesforce Commerce Cloud has become the best solution for delivering the ultimate shopping experience to the customers. By…