-
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, 2 months ago by
Aditya.
-
This discussion was modified 4 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 10 Forecasted CRM Trends In 2021 | Salesforce
Times are changing, which means implementing innovations and new ways of interacting with this simple business tool for CRM software users. What’s going to be…
How to Use Salesforce Marketing Cloud and 15 Surprising Benefits
Salesforce Marketing Cloud provides a variety of tools for creating personalized journeys that are relevant to your audience. This article will explore some of the advantages…
Change Your Business Game With Salesforce and Vlocity
Salesforce has been one of the most well-known CRM platforms used by thousands of businesses, accountants, and firms all over the world. With over 150,000…
Popular Salesforce Videos
Creation Of An Object In Salesforce | Salesforce Custom Objects
In this video, you will learn how to create a custom object in Salesforce, along with verification of the custom object in Salesforce. The following…
Everything New in Salesforce Developer Tools
Your productivity starts and ends with the tools you use. Learn how Salesforce Developer Tooling can help you collaborate more effectively with your whole team.…
Slack API Integration for Salesforce Marketing Cloud
Connect Salesforce Marketing Cloud and Slack the way you want. Watch this video to learn all about Slack API Integration for Salesforce Marketing Cloud. If…