-
Why future methods must be static in Salesforce?
Why future methods must be static in Salesforce?
-
2 Replies
-
Future methods can be accessed from any class and not depend on any class instance hence it is declared as Static.
- [adinserter block='9']
-
Because Future methods can be accessed from any class and not depend on any class instance.
Log In to reply.
Popular Salesforce Blogs
How Can Hiring A Salesforce Consultant Increase Your Business ROI?
What does Return on Investment mean? Return on Investment (ROI) is a measurement of performance that helps in calculating the efficiency of an investment. With…
OAuth 2.0 Device Authorization Flow in Salesforce
For input-restricted devices that connect to the Internet, instead of authenticating the user directly, the device prompts the user to go to a link on…
How to insert sObjects records using Visualforce Remote Objects ?
Visualforce Remote Objects: Visualforce Remote Objects are proxy objects that enable basic DML operations on sObjects directly from JavaScript. Remote objects don't require @RemoteAction methods…
Popular Salesforce Videos
UiPath automation for Salesforce | REST API commands | OAuth2 | Download files | Without activity
How to send a raw REST API command from UiPath to Salesforce without using custom activities. 0:00 Intro 1:35 OAuth2 4:10 Download files from a case, opportunity, account,…
Understanding Traditional AI vs. Generative AI | Explained Simply
Ever wondered how computers can be taught to think? Or how they create art, music, and stories on their own? If you're curious about these…
How to Manage Your Data and Contacts in Salesforce Marketing Cloud
Learn how contacts are counted and how data is structured in Marketing Cloud. This video explores how Marketing Cloud receives data from many sources and…
