-
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 ago by
Aditya.
-
This discussion was modified 6 years 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
7 Signs Your Company Needs a Salesforce Consulting Partner
1. Struggling with Salesforce Adoption One of the most common challenges businesses face is low adoption rates of Salesforce among their teams. Despite its powerful…
Key Management in Shield Platform Encryption | Salesforce Security Guide
Shield Platform Encryption licenses Salesforce head to deal with the life cycle of their information encryption keys while shielding those keys from unapproved access. To…
Mastering Salesforce Data Migration: A Complete Guide
Salesforce is a leading CRM platform that helps businesses manage their customer relationships efficiently. However, moving data into Salesforce can be tricky. This guide will…
Popular Salesforce Videos
Salesforce Validation Rules - Keep your Data Clean
Watch this short video for just over 2 minutes and learn how to keep your Salesforce data clean? The answer is simple: Use field validation…
Salesforce User Experience UX Designer Certification
The Salesforce User Experience (UX) c is designed for individuals who have at least 6 months in UX design and 3–6 months’ experience utilizing UX…
Fillable PDFs for Salesforce Field Service
The ability to generate fillable PDFs for Salesforce Field Service can be a powerful tool. We demonstrate how to use PDFLib, a JavaScript library that…
