Create a global value set in Setup, then base one or more picklist fields on it so they all share the same governed list of values.
- Open Picklist Value Sets
From Setup, type Picklist in the Quick Find box and select Picklist Value Sets. The page lists existing global value sets and standard value sets.
- Create the global value set
Next to Global Value Sets, click New. Enter a label, which appears in Setup and when someone builds a picklist on this set. Type the values one per line.
- Set ordering and default
Optionally choose to sort the values alphabetically and to use the first value in the list as the default. Save the set. You can edit the API name and description from its detail page.
- Base a field on the set
Create or edit a custom picklist field, and choose to use a global value set, then pick the one you just made. The field now reads its values from the set. Repeat on other objects to share the same list.
- Maintain values centrally
To change values later, open the value set detail page and use the Values related list to add, deactivate, replace, or reorder entries. The change reaches every field that uses the set.
The display name of the value set in Setup and in the picklist creation screen. Pick something that reads as a reusable list, like Industry or Region.
The entries themselves, one per line. A global value set is restricted, so only these approved values can be saved on any field using it.
Orders the values A to Z for users instead of keeping your entry order. Leave it off when a deliberate sequence such as a status flow matters.
Sets the top value as the default selection on fields built from the set. Useful when one option is the common starting state.
- Once a field uses a global value set, you can no longer edit that field's values on the field itself. Edit them on the value set, and the change affects every field that references it.
- Global value sets are restricted, so integrations cannot introduce new values. Reconcile any values a data load was silently adding before you promote a field, or saves will fail.
- Adding a value to the set does not add it to every record type. You still enable the new value per record type where it should appear.
- When deploying with change sets, include the value set or deploy it first. A field that references a missing global value set fails with a cannot be resolved error.