Newer Version Available
GlobalValueSet
File Suffix and Directory Location
GlobalValueSet components have the suffix .globalValueSet and are stored in the globalValueSets folder.
Version
GlobalValueSet components are available in API version 38.0 and later. In API version 37.0, this component is the GlobalPicklist type.
Fields
| Field Name | Field Type | Description |
|---|---|---|
| customValue | CustomValue[] | Requires at least one value. The list of values, or “global value set,” that’s defined for a global picklist. The global value set is inherited by any custom picklist field that uses that value set. Each value is of type customValue. A global value set can have up to 1,000 total values, including inactive values. |
| description | string | It’s useful to state the global value set’s purpose and which objects it’s intended for. Limit: 255 characters. |
| masterLabel | string | Required. A global value set’s name, which is defined when the global value set is created. Appears as Label in the user interface. |
| sorted | boolean | Required. Indicates whether a global value set is sorted in alphabetical order. By default this value is false. |
Declarative Metadata Sample Definition
This UpsellGlobal.globalValueSet is an example of a GlobalValueSet component.
This example package.xml references the previous definition.
Any global value set created in API version 57.0 or later automatically has the __gvs suffix appended to the developer name. When you make any CRUD-based call with the GlobalValueSet type, you must append the suffix to the fullName field when you reference the type.
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.