Picklist Value Sets
Picklist Value Sets is a Setup page for creating and managing global picklist value sets that can be shared across multiple picklist fields on different objects.
Definition
Picklist Value Sets is a Setup page for creating and managing global picklist value sets that can be shared across multiple picklist fields on different objects. When a value is added to or removed from a global value set, the change is automatically reflected on all fields using that set.
In plain English
“Here's a simple way to think about it: Picklist Value Sets keep parallel dropdowns from drifting apart. Industry on Account, Industry on Lead, Industry on Opportunity - same values, one canonical list, kept consistent automatically.”
Worked example
The admin at NexGen Logistics creates a Global Picklist Value Set called "Regions" with values: North America, Europe, Asia Pacific, Latin America, and Middle East. She uses this value set on the Region field on Account, Lead, and Opportunity objects. When the company expands into Africa, she adds the value once and it appears on all three objects instantly.
Why Picklist Value Sets keep parallel dropdowns from drifting apart
When the same set of values needs to appear in picklists on multiple objects (Industry on Account, Industry on Lead, Industry on Opportunity), the naive approach is to create three separate picklists with the same values and hope they stay in sync. They don't. Picklist Value Sets gives you a global value set instead - one canonical list, referenced by every picklist that uses it, kept consistent automatically. Add or remove a value once, and every dependent picklist updates.
The reason this earns adoption is that the alternative is a maintenance bug waiting to happen. Inconsistent Industry values across Lead, Account, and Opportunity break reports, segmentation, and any cross-object workflow that joins on the field. Migrate existing inline picklists to value sets the first time you notice drift, build new picklists against value sets by default, and audit the catalog to catch picklists that should be consolidated but aren't.
How to set up Picklist Value Sets
Picklist Value Sets (Global Picklists) are reusable lists of values shared across many picklist fields — "Country," "US State," "Industry." Adding a value to the set propagates to every field that uses it. They enforce data consistency and let admins maintain a single source of truth.
- Open Setup → Picklist Value Sets
Setup gear → Quick Find: Picklist Value Sets → Picklist Value Sets.
- Click New
Top-right of the list.
- Set Label and Name
Convention: descriptive of the values — "Country List," "US State," "Industry Categories."
- Add values, one per line
Type or paste values — one per line. Each value's Label and API Name auto-derive.
- Set Default value (optional) and Sort
Default appears first when no value is set. Sort: Alphabetical / In order entered.
- Save
Picklist Value Set is created. Now use it on a picklist field.
- When creating a Picklist field on any object: tick Use a global picklist value set
Object Manager → object → Fields → New → Picklist → tick Use a global picklist value set → pick this set. The field is now bound to the global values.
One per line. Label + API Name + Default + Active.
When ticked, API submissions of unlisted values are blocked. When unticked, unlisted values can flow in via API but not via UI.
Alphabetical / In order entered.
Selected when no value is set on a new record.
- Adding a value to the Picklist Value Set propagates to every field using it instantly. Removing a value flags affected records' values as Inactive — not erased, but hidden in the picker.
- Restrict to defined values blocks unlisted API values. Without it, integrations can write any string into the field, defeating the consistency point. Always tick Restrict for new picklists.
- Record Types CAN'T filter values from a global picklist — record type filtering only works on local picklists. If you need per-record-type values, the picklist must be local, not global.
How organizations use Picklist Value Sets
Migrated 8 inline Industry picklists to one Value Set; reporting cross-object Industry breakdowns finally works correctly.
Country code Value Set replaces 15 separate country picklists; cleanup project saved hundreds of hours of manual reconciliation.
Severity-level Value Set used across Cases, Incidents, and Tickets; cross-object reporting is now consistent.
Trust & references
Straight from the source - Salesforce's reference material on Picklist Value Sets.
- Create a Global Picklist Value SetSalesforce Help
Test your knowledge
Q1. What is the primary benefit of Picklist Value Sets for Salesforce administrators?
Q2. In which area of Salesforce would you typically find Picklist Value Sets?
Q3. Can a Salesforce admin configure Picklist Value Sets without writing code?
Discussion
Loading discussion…