-
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
Whitelist IP Address in Salesforce
How to Whitelist IP Address in Salesforce! Whitelisting basically ensures that the firewall will not block your browsers from loading the page. Don’t forget to…
Drive Financial Growth with Sage Intacct Consulting Benefits
Businesses must keep ahead of the curve in an ever-changing business climate by using the appropriate solutions. Sage Intacct, a financial management tool designed to…
Open Web Application Security Project | Salesforce Security Guide
Why Is OWASP Important to You? OWASP represents the Open Web Application Security Project. This open-source project gets the news out about application security weaknesses,…
Popular Salesforce Videos
Salesforce Winter'21 New Apex Features
So wait is over... In this tutorial we would discuss many new Apex Features as below : Use Safe Navigation Operator PATCH HTTP Method in…
Get a Salesforce Developer Job in 5 Steps | For Freshers | For Admins | For Non-SFDC People
In this video, We will be talking about some tips to get your first job as a Salesforce Developer. If you are a recent graduate,…
After Triggers | Trigger in Salesforce - Part 2
In this video, we are going to look into - After Trigger with Example, Our Scenario is - For After Insert Whenever my account record…
