The method of selecting the translation below is deprecated. Please refer to the new method of deploying translations documented here: https://docs.essentials.copado.com/en/articles/4109734-deploy-translations

The translation is similar to Profile in that they are variable content. That means to deploy translation, you would need to select both the language and the object/fields to be included for that language.

In the example below, we select language "fr" and a "Dynamic_Form__c" object. When we retrieve the package.xml, we can see the full object translation in French.

Screen_Shot_2019-10-04_at_9.03.17_AM.png

If you want to deploy translation just for a subset of fields, you can de-select the object and select the fields instead, like below.

Screen_Shot_2019-10-04_at_9.08.07_AM.png

Copado Essentials also gives you finer control of what to include in the package using the exclusion option. You can learn more about the exclusion option here: https://clickdeploy.zendesk.com/hc/en-us/articles/360000818835-Release-19-3-2-Gain-more-control-and-flexibility-with-profile-and-record-type-deployments

For dynamic metadata types like Profile, Record Type, or Translation, it is often useful to know exactly what is in the package before you deploy. To do this, simply click on More > Download Package.

Please note that the above method of deploying translation is only applicable for an Org-to-Org deployment flow. For a Git-to-Org deployment flow, selective deployment of translations from Git is currently not supported.

Did this answer your question?