Create a Global Picklist Value Set so several fields share one governed list of enumeration values. Build the set once, then base each picklist field on it. Editing the set later updates every field that points at it.
- Open Picklist Value Sets in Setup
In Setup, use Quick Find to open Picklist Value Sets. This is where global sets live, separate from any one object. Click New next to Global Value Sets to start a fresh list.
- Name the set and enter values
Give the set a clear label and API name, then type each value on its own line in the order you want them shown. The set is restricted by nature, so only admins can change these values later.
- Create a picklist field based on the set
On the target object, add a new Picklist field. When asked for values, choose the option to use a global value set and select the one you created. Repeat on every object that needs the same list.
- Verify the shared behavior
Edit one value in the set and confirm the change appears on every field that inherits it. Reports and filters now reference one consistent list across the org.
The human-readable name of the value set shown to admins. Pick something that names the concept, like Industry or Country.
The list of allowed entries, one per line, with an active or inactive state each. Combined active and inactive values cap at 1,000 per set.
The choice, when building a picklist field, to base it on this global set instead of local values. This association cannot be undone later.
- You cannot reverse a field's association with a global value set. Switching sets means deleting and recreating the field.
- A global value set is always restricted, so off-list values are rejected on every path, including the API.
- An org allows up to 500 global value sets, and each set holds at most 1,000 active and inactive values combined.