Working with Translations in ARM
PreviousMetadata comparison between two Salesforce OrgsNextRevision Range & Release Label Deployment
Last updated
Last updated
Translation feature can help you translate almost everything in your organization ranging from Salesforce custom objects, fields, labels, etc. This provides users with different languages to interact with Salesforce.
In order to translate custom objects for a variety of languages, you need to commit the following components.
Select the CustomObject metadata type and select the specific custom objects that you want to move the translation.
Select the CustomObjectTranslation metadata type and select the translations associated with the custom object.
Point to Note:
The translation will not take place and nothing will be retrieved if you merely use the CustomObjectTranslation metadata type and leave out the Custom Object.
The translation should be activated for the custom object in the destination org.
To commit and deploy custom field translations with ARM, you need to commit the following components.
Select the CustomField metadata type and select the specific custom fields that you want to move the translation.
Select the metadata type CustomObjectTranslation and select the members associated with the custom object.
Troubleshooting:
In some circumstances, the CustomObjectTranslation might just have the opening and closing xml tags. In this situation, we advise you to do a commit while selecting the Review Artifacts option, allowing you to inspect the contents of the files before committing them.
Translations for custom labels determine what text to display for the label’s value when a user’s default language is the translation language.
To commit or deploy custom label translations with ARM, you need to commit the following components.
Select the name of the custom label you want to translate available under the CustomLabel metadata type.
Look for the Translation metadata type and select the language from the list.
A field set is a group of different fields. For example, a field set that contains fields describing a user's first name, last name, occupation, etc.
In order to commit and deploy field set translations with ARM, you need to commit the following components.
Select the FieldSet metadata type and select the specific field set(s) that you want to move the translation.
Select the metadata type Translations and select the language you want the translations to be moved. This deploys the field sets along with the translations for the language selected.
In order to commit and deploy standard value set translations with ARM, you need to commit the following components.
Select the StandardValueSet metadata type and select the specific standard value sets that you want to move the translation.
Select the StandardValuesetTranslation metadata type and select the respective metadata members from the list.
Select the metadata type Translations and select the language you want the translations to be moved. This deploys the standard value sets along with the translations for the language selected.
In order to commit and deploy global value set translations with ARM, you need to commit the following components.
Select the GlobalValueSet metadata type and select the specific global value sets that you want to move the translation.
Select the GlobalValuesetTranslation metadata type and select the global value set translations metadata members from the list.
Select the metadata type Translations and select the language you want the translations to be moved. This deploys the global value sets along with the translations for the language selected to the Version Control branch.
NOTE: The API can’t perform destructive changes with the translation value. The API can add existing <translation> to custom object translation but not delete them.
