Contents
Why future methods do not accept sObject?
The reason why sObjects can’t be passed as arguments to future methods is because 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.
Can we pass sObject in future method?
Normally, we cannot pass the sObject list to the future methods. We can only pass the primitive data types to the future methods, but by using the simple technique, we can overcome this limitation with Salesforce.
Why future methods can’t take standard or custom objects as arguments?
The reason why objects can’t be passed as arguments to future methods is because the object can change between the time you call the method and the time that it actually executes. Remember, future methods are executed when system resources become available.
What are future methods in Salesforce?
Future Methods in Salesforce using @future annotation A future method runs in the background, asynchronously. You can call a future method for executing long-running operations, such as callouts to external Web services or any operation you’d like to run in its own thread, on its own time.
Are there any unsupported parameters for the future method?
@Future parameters must be primitive data types, arrays of primitive data types, or collections of primitive data types. Methods with the future annotation cannot take sObjects or objects as arguments. There is the workaround using JSON serialization/deserialization so that you can pass the serialized string of your objects to the future method.
Can a @ future method take a sobject?
So I would suggest passing a Set & requerying for the sObject records in your @future method. @Future parameters must be primitive data types, arrays of primitive data types, or collections of primitive data types. Methods with the future annotation cannot take sObjects or objects as arguments.
Are there any unsupported parameter types in apex?
Error: Compile Error: Unsupported parameter type LIST at line 3 column 30 Methods with the future annotation must be static methods, and can only return a void type. The specified parameters must be primitive data types, arrays of primitive data types, or collections of primitive data types.
Can a future method invoke another future method?
However, a future method can’t invoke another future method. Methods with the future annotation have the following limits: Asynchronous calls, such as @future or executeBatch, called in a startTest, stopTest block, do not count against your limits for the number of queued jobs.