-
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
3 Tactics to Optimize Your Salesforce Implementation
Salesforce implementation requires substantial planning and investment. While most businesses invest heavily during the implementation phase, only a significant proportion of them reap above satisfactory…
What AI Capabilities does Salesforce brings to you?
AI or Artificial Intelligence is the technology of this era and is giving a new shape and level to customer’s expectations. Now, AI has entered…
Salesforce Stripe Payment Processing
In today’s fast-paced digital world, businesses of all sizes constantly seek ways to provide a seamless customer experience. One crucial aspect of this experience is…
Popular Salesforce Videos
Apex Scheduler in Salesforce | Asynchronous Apex
Asynchronous Apex 1. Apex Scheduler 2. Interfaces in Apex Scheduler 3. Making callout using Apex Scheduler 4. Points to Remember Upcoming Video on How to…
Salesforce SOAP API integration using Partner WSDL
This video is another one on our Salesforce Integration learning video series, through this video our experts will be going to demonstrate how to use…
Why iCompliance Trusts TechForce Services for Salesforce Managed Services | Client Testimonial
At iCompliance, delivering trusted AFSL compliance services requires seamless operations and efficient technology. That’s why they turned to TechForce Services for Salesforce Managed Services. In…
