-
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 5 years, 10 months ago by
Aditya.
-
This discussion was modified 5 years, 10 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
Quick Tips for Managing Multiple Marketing Cloud Instances
It requires art to manage multiple cloud instances, specifically when aiming to maintain efficient, consistent, and effective communication across different platforms. Marketing cloud platforms include…
A Guide to Integrate Salesforce Service Cloud with Jira
Joel is the head of customer support at a leading cybersecurity software provider company and he manages a team of over 400 service reps. His…
Detailed Overview of Salesforce Einstein 1 Studio
In the recent stage of AI growth, customization has been at the forefront of innovation. Salesforce has made an advancement in this trend, presenting Einstein…
Popular Salesforce Videos
How Do You Create Sandboxes in a Professional Edition in Salesforce?
Eric Stafford asks, “How do you create Sandboxes in a Professional Edition?” and gets an expert answer and demo from LeeAnne Rimel, Architect, Admin Evangelism…
Scheduled Actions Workflow Rules, Process Builder and Lightning Flow
Time-dependent actions are executed at a specific time, such as 10 days before a record's close date. When that specific time passes, the workflow rule…
Salesforce Acquires Slack
When Salesforce bought Slack earlier this week for $27.7 billion, it was in some ways the end of a startup fairytale. Slack was the living…
