-
Why sObjects can’t be passed as arguments to future methods in Salesforce?
Why sObjects can’t be passed as arguments to future methods?
-
This discussion was modified 6 years, 2 months ago by
Aditya.
-
This discussion was modified 6 years, 2 months ago by
-
1 Reply
-
The sObject might change between the time you call the method and the time it executes. In this case, the future method will get the old sObject values and might overwrite them. To work with sObjects that already exist in the database, pass the sObject ID instead (or collection of IDs) and use the ID to perform a query for the most up-to-date record. The following example shows how to do so with a list of IDs.
Log In to reply.
Popular Salesforce Blogs
Top 5 Benefits of Salesforce Commerce Cloud
As the number of online shoppers continues to increase rapidly, businesses must adapt to this growing market. To attract customers and expand their online presence,…
Meet Einstein GPT, the first generative AI for CRM
Since its release in November 2022, Chat GPT has become a buzzword - over a million people signed up to use it in just five…
5 Reasons To Use Salesforce As Your Healthcare CRM
Although many may argue that businesses across all sectors are similar when it comes to certain factors or essential operational aspects, there are some businesses…
Popular Salesforce Videos
Salesforce Connections 2018 Keynote - Ch. 3: Adidas Is A Trailblazer
Salesforce Connections 2018 Keynote – Ch. 1: Corporate Positioning Salesforce Connections 2018 Keynote – Ch. 2: Ticketmaster Is A Trailblazer Salesforce Connections 2018 Keynote –…
7 Tips To Choose The Right CRM For Your Business
A Customer Relationship Management (CRM) system can be overwhelming to choose from. You have so many options to choose from, each offering different tools and…
Marketing Cloud | Salesforce Send Email
There are two ways to send an email in Marketing Cloud; Guided Send Wizard & Salesforce Send Email. The benefit of the Salesforce Send Email…
