GlobalValueSetTranslation
File Suffix and Directory Location
GlobalValueSetTranslation components have the suffix .globalValueSetTranslation and are stored in the globalValueSetTranslations folder.
Translations are stored in a file with a format of ValueSetName-lang.globalValueSetTranslation, where ValueSetName is the global value set’s name, and lang is the translation language.
Version
GlobalValueSetTranslation components are available in API version 38.0 and later.
Fields
| Field | Field Type | Description |
|---|---|---|
| valueTranslation | ValueTranslation[] | The translated name of a value in a translated global value set. Each valueTranslation is paired with a masterLabel, which is the original (untranslated) name of the value. |
ValueTranslation
The original value name and the translated value name in a translated global value set.
| Field | Field Type | Description |
|---|---|---|
| masterLabel | string | Required. The original (untranslated) name of a value in a global value set. Each valueTranslation has a masterLabel paired with its translation. |
| translation | string | The translated name of a value in a translated global value set. |
Declarative Metadata Sample Definition
This example shows a GlobalValueSetTranslation component. When a value isn’t translated, its translation becomes a comment that’s paired with its masterLabel.
This example is a package.xml that references the previous definition.
Wildcard Support in the Manifest File
This metadata type supports the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.