-
Why objects can’t be passed as arguments to future methods in Salesforce?
why objects can’t be passed as arguments to future methods ??
-
1 Reply
-
The reason why Salesforce objects cannot be passed as arguments to future methods is that the object can change between the time you call the method and the time it actually executes. Because future methods are executed when system resources become available. In this case, the future method will get the old sObject values and might overwrite them.
Log In to reply.
Popular Salesforce Blogs
Streamlining Financial Advisory Services with Salesforce
Introduction Regarding financial advisory services, efficiency is pitted against personalization in a landscape governed heavily by regulation. The drivers have converged and it is a…
CRM Implementation Made Easy: A Step-by-Step Guide for Success
According to CIO magazines, almost one-third of the CRM efforts fail. But why? Well, the wrong CRM implementation makes it difficult for businesses to manage…
Data Management in Salesforce - Here is All You Need to Know
This is the important part to understand clearly as an administrator. In this blog we are going to learn about how the data is imported…
Popular Salesforce Videos
Handle Events in Lightning Web Components | Salesforce Tutorial
Watch this video and learn about the following: Create an app that includes multiple components. Describe the file structure of a complex component. Handle events.
Cross Component Communication with Custom Events | Salesforce Developer Quick Takes
In this Quick Take, we will learn how to take Custom Events and apply them to a common use case. We’re first going to take…
Salesforce Spring 22 Treasure Hunt for Flow | Migrate your Workflow Rules to Flows
Salesforce Spring 22 Treasure Hunt for Flow 0:00 Register for pre-release org 0:27 Flow Trigger Explorer 2:07 Auto-Layout and Freeform option as Picklist 3:00 Set…
