-
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 4 years, 11 months ago by
Aditya.
-
This discussion was modified 4 years, 11 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
Sort Picklist Values in Lightning Component | Salesforce Tutorials
In this article, you will learn to sort the values in Picklist in Lightning Component. You just have to add an additional line to your…
Salesforce Lightning Dialer | Boost Sales productivity by making hassle-free calls
In spite of the rapid and continuous advancement in the realms of communication with new platforms and new channels mushrooming all around us, telephones still…
Salesforce for Public Sector: Enhancing Public Services with Salesforce
The public sector is no exception - and it is changing at a breakneck speed in an era when technology is revolutionizing every facet of…
Popular Salesforce Videos
Salesforce Public Groups and Queues
In this video, Bhavesh Jain demonstrates how to create Salesforce public groups and how they can be used, as well as provides an understanding of…
Salesforce QA DEMO | Video Tutorial Guide
In this video, SV Tech Soft provides a Salesforce QA DEMO. This is a great opportunity to see how the software works and how it…
Unleash the Power of Compare Tables | Salesforce Video
In this video, you will learn how to use compare tables to calculate complex calculations quickly, which you can then use to visualize your data.…
