Master Picklist
A Master Picklist in Salesforce is the canonical, complete list of values for a picklist field, defined at the field level and used as the source for any record type that restricts the picklist's values.
Definition
A Master Picklist in Salesforce is the canonical, complete list of values for a picklist field, defined at the field level and used as the source for any record type that restricts the picklist's values. Each picklist field has exactly one Master Picklist; record-type-specific picklist value sets are subsets of the master. The Master Picklist is where new values are added or retired; record type configurations then choose which subset of master values appear for that record type.
The concept matters because picklist administration spans two layers: master-level value management (what is the full list of possible values?) and record-type-level value selection (which values does this specific record type expose?). Confusing these layers produces frequent administrative mistakes: a value added to a record type without first adding to the master fails silently; a value removed from the master propagates to all record types that included it. Understanding the master/record-type relationship is foundational to picklist administration.
How the Master Picklist relates to record types
Master versus record-type values
The Master Picklist holds every possible value the field can ever have. Each record type for the object then configures which master values it exposes. Values cannot appear on a record type unless they exist in the master. Removing a value from the master removes it from every record type. The master is the source of truth; record types are filtered subsets.
Adding values
To add a new picklist value, add it to the Master first, then enable it on the relevant record types. Two-step process: field-level edit to add to master, record-type-level edit to expose. Skipping the second step adds the value to the master but no record type displays it; users do not see the new value until the record type enable step.
Deactivating values
Values can be deactivated rather than deleted. Deactivation removes the value from picklist dropdowns going forward but preserves historical records using the value. Active records continue to display the old value but cannot be edited to keep it. Deletion is more aggressive: it removes the value from records too, replacing with blank or a default. Deactivation is the safer path for retiring values.
Global Value Sets
Global Value Sets are shared picklist values used across multiple fields. The Global Value Set acts as a higher-level master, with field-level masters referencing it. Changes to the Global Value Set propagate to every field using it. Useful for consistent values across objects (Region, Country code, Status); for one-off picklists, the field-level master is sufficient.
Sort order and default value
The master controls the default sort order of values in picklist dropdowns. Record types inherit the master sort order unless overridden. The default value (the value pre-populated on new records) is set per record type, not at the master level. Different record types can have different default values from the same master.
API name and label
Each picklist value has an API name (used in code and integrations) and a label (shown to users). The master controls both. Changing the label changes display everywhere; changing the API name breaks any code or integration referencing the old name. Plan API name changes carefully; relabel rather than rename when possible.
Restricted picklist behavior
Picklist fields can be marked Restricted, meaning users cannot enter values outside the master. Without Restricted, users can type values that are not on the master; the value is stored but appears as an outlier in reports. Most production picklists should be Restricted to enforce data quality; reserve unrestricted for migration scenarios.
Manage Master Picklist values
Managing picklist values involves master-level changes and per-record-type configuration. The steps below cover both halves.
- Open the field
Object Manager > Object > Fields and Relationships > Picklist field > Edit.
- Add or edit master values
In the Values section, add new values, deactivate retired ones, or reorder. Changes to the master propagate to all referencing record types.
- Mark Restricted (recommended)
Check Strictly enforce picklist values. Prevents user-typed values outside the master.
- Save the master changes
The master is updated. Record types do not automatically expose new values; the next step is needed.
- Configure per record type
For each record type on the object, edit the picklist value selection. Enable the new values on relevant record types; leave unrelated record types unchanged.
- Set default value per record type
Optionally set a different default value for each record type. The default is per record type, not at the master.
- Test from a sample user
Use Login As to confirm the new values appear on record creation and the default behaves as expected.
Add a new value to the master.
Remove from picklist going forward; preserve historical records.
Prevent user-typed values outside the master.
Control display order of values in dropdowns.
Use shared values across multiple fields.
- Add to master before enabling on record types. Skipping the master step makes the value invisible to users.
- Deleting values from the master replaces them on records. Deactivation is safer; deletion is irreversible at the record level.
- API name changes break integrations. Relabel rather than rename when possible.
- Unrestricted picklists allow user-typed values. Defeats the data quality purpose; mark Restricted in production.
- Default value is per record type, not at the master. Configure separately for each record type.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Master Picklist?
Q2. How are master picklists used with record types?
Q3. What's the value of master picklists with subsets?
Discussion
Loading discussion…