Picklist Settings
Picklist Settings is a Setup page where administrators configure global behavior for picklist fields across the org, including whether to sort picklist values alphabetically or in a custom order, and whether to restrict picklist field values to only those defined by the administrator.
Definition
Picklist Settings is a Setup page where administrators configure global behavior for picklist fields across the org, including whether to sort picklist values alphabetically or in a custom order, and whether to restrict picklist field values to only those defined by the administrator.
In plain English
“Here's a simple way to think about it: Picklist Settings shape how every dropdown in the org behaves. Sort order, restriction policy, allowed-values handling - toggles that change the behavior of thousands of fields at once.”
Worked example
The admin at Summit Retail opens Picklist Settings and enables the "Restrict picklist to the values defined in the value set" option to prevent users from entering arbitrary values via the API. This ensures data consistency by guaranteeing that every Lead Source value in the system matches one of the 10 predefined options.
Why Picklist Settings shape how every dropdown in the org behaves
Picklist fields are everywhere - every Stage, Type, Industry, Status field is a picklist somewhere. Picklist Settings is the page where org-wide behaviour for all of them gets set. Should values sort alphabetically by default or in the admin-defined order? Should existing data be allowed to keep values that are no longer in the picklist? Should the platform restrict picklists tightly to defined values? Each toggle changes the behaviour of thousands of fields at once.
The reason it's worth visiting once and configuring deliberately is that the choice cascades. Restrict picklists strictly and you'll catch typos at data load time; relax the restriction and you'll allow ad-hoc values that produce report misalignment later. Most orgs benefit from strict restriction at the org level, with explicit exceptions for specific picklists where business processes legitimately need free-form values.
How to set up Picklist Settings
Picklist Settings controls global picklist behavior — what happens to inactive values, whether unrestricted picklists let API submissions through, and similar org-wide toggles. Small page, but the toggles touch every picklist field in the org.
- Open Setup → Picklist Settings
Setup gear → Quick Find: Picklist Settings → Picklist Settings.
- Click Edit
Top-right of the page.
- Configure Restricted Picklist behavior
When picklists are Restricted, API submissions of unlisted values are blocked. Decide: block always, log warnings, or allow?
- Configure inactive value behavior
When a picklist value is deactivated, what happens to existing records using that value? (Stay as-is by default; some configurations move them.)
- Tick Enforce Restriction at API Level
Strongly recommended. Without this, integrations can write any string to a picklist field, creating data quality issues.
- Save
Settings apply to all picklists in the org.
When ticked, API submissions of unlisted values fail validation. Recommended ON.
What happens to existing records when a value is deactivated.
How picklist values appear by default — Alphabetical / Manual.
- Without Enforce Restriction at API Level, restricted picklists are restricted in UI only. Apex / API can still write any string. The restriction is a UX hint, not a data-quality enforcement.
- Deactivating a picklist value doesn't remove it from existing records — they keep the inactive value. Reports including those records show the inactive value normally.
- Global Picklist Value Sets have their own restriction behavior independent of the org-level setting. Check both layers when debugging unrestricted picklists.
How organizations use Picklist Settings
Strict picklist restriction enabled org-wide; data quality improved as ad-hoc values stopped.
Picklist Settings audited during compliance review; consistency across all picklist fields verified.
Test your knowledge
Q1. Why is understanding Picklist Settings important for Salesforce admins?
Q2. Can a Salesforce admin configure Picklist Settings without writing code?
Q3. In which area of Salesforce would you typically find Picklist Settings?
Discussion
Loading discussion…