In most cases, you don't need to worry about which API version to choose when deploying using Gearset - we'll automatically pick the highest API version that's supported by both the source and target of your comparison.

In the case of source control or file-based comparisons, Gearset will try to detect what API version your metadata is in, by looking in the package.xml file. If there's no package.xml  file present, Gearset will try to deduce the version based on the types of metadata in the repository. If Gearset still can't tell, it will default to assuming your metadata is in API version 44. You can learn more about how we detect API versions in our blog.

Overriding the API version 

Occasionally it's useful to be able to override the API version that Gearset has picked. This is done through the metadata filter dialog.

On the Compare and deploy page, open the metadata filter menu in the bottom right of the screen, and select Manage custom filters...:

Use the dropdown at the bottom of the Manage custom filters dialog to select an API version for your comparison:

This API version will now be used for retrieval from Salesforce, and any deployments that result from the comparison.

Optionally, you can save this selection into a custom filter for re-use later and to share the setting with the rest of your team. For more information on this, see the custom metadata filters article.

Did this answer your question?