function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
SFDC_shubhSFDC_shubh 

what is the use of API Version in Developer Console..?

Khan AnasKhan Anas (Salesforce Developers) 
Hi,

Greetings to you!


Every time Salesforce releases a new application version, its API version is updated as well. At the time of writing, we had just released Winter 19, which introduced API version 44.

This API version means that when you deploy changes using the API (e.g. using the Eclipse Force.com IDE plugin) and use version 44, your target SFDC Org will deploy these changes with the logic it associates with that particular version of the MetaData API (44). So for example, version 44 introduces a new field on the object ApexPage called isConfirmationTokenRequired. If you try to upload an Apex Page which contains that field and you are trying to do so using API version 43, your deployment script will fail because that field is not known for that API Version. On the other hand, if you would upload the same file specifying API version 44, it would work fine.

A key principle to understand is that whilst SFDC may release version 44 of the API, the deployment logic associated with version 43 is still available for use as long as you force the API to use version 43.

I hope it helps you.

Kindly let me know if it helps you and close your query by marking it as solved so that it can help others in the future. It will help to keep this community clean.

Thanks and Regards,
Khan Anas
 
Ajay K DubediAjay K Dubedi
Hi Subh,

Every time Salesforce releases a new application version, its API version is updated as well. 
At the time of writing, we had just released Summer 2013, which introduced API version 28.
This API version means that when you deploy changes using the API (e.g. using the Eclipse Force.com IDE plugin)
and use version 28, your target SFDC Org will deploy these changes with the logic it associates with that particular 
version of the MetaData API (28). So for example, version 28 introduces a new field on the object ApexPage called
isConfirmationTokenRequired. If you try to upload an Apex Page which contains that field and you are trying to do so using
API version 27, your deployment script will fail because that field is not known for that API Version. 
On the other hand, if you would upload the same file specifying API version 28, it would work fine.
A key principle to understand is that whilst SFDC may release version 28 of the API, the deployment logic
associated with version 27 is still available for use as long as you force the API to use version 27. 

For more information go through the link below:
https://developer.salesforce.com/blogs/developer-relations/2013/10/api-versions-and-the-salesforce-metadata-api.html

Thanks,
Ajay Dubedi