Picklist Settings
Picklist Settings is the collection of configuration options in Salesforce that control how a picklist field behaves: whether its values are restricted to a defined list, how those values sort, which value is the default, and how it relates to other fields.
Definition
Picklist Settings is the collection of configuration options in Salesforce that control how a picklist field behaves: whether its values are restricted to a defined list, how those values sort, which value is the default, and how it relates to other fields. In modern Salesforce, these options live on the field itself and on the value set that feeds it, not on a single org-wide Setup page.
The settings matter because picklists drive reporting, automation, and data quality across the whole org. A field with a strict value set rejects bad input at save time. A loosely controlled one lets typos and stale values pile up. Picklist Settings is where an admin decides which way each field leans.
How the settings come together on a picklist
Restricting a picklist to its value set
The most consequential picklist setting is the checkbox labeled "Restrict picklist to the values defined in the value set." When you enable it, the field becomes a restricted picklist. Users and integrations can only save one of the active values you defined. Any other input, whether from a Data Loader file, an API call, or a Flow, fails with a "bad value for restricted picklist field" error. When the box is clear, the picklist is unrestricted, and an import can quietly introduce values that were never on the list. Those orphan values still show up in reports and filters, which is how a single field ends up with three spellings of the same status. Most teams turn restriction on for fields that feed dashboards or automation, because catching a bad value at save time is far cheaper than cleaning it up later. You can switch an existing field between restricted and unrestricted, but moving to restricted while non-conforming data already exists needs a cleanup pass first. Restriction is also what makes a picklist a reliable input for record-triggered automation and roll-up logic.
Sorting and default values
Two display settings shape how a picklist reads to end users. The first is the "Display values alphabetically, not in the order entered" option, reached through the Reorder screen on a field or as "Sort values alphabetically" on a global value set. By default Salesforce shows values in the manual order you arranged. Turn on alphabetical sorting and the list reorders itself, which keeps long lists tidy but removes your ability to surface the most common choice at the top. New or edited values do not sort automatically when manual order is in effect, so you reorder them yourself. The second setting is the default value. On a global value set you can choose "Use first value as default value," and on a standard or local picklist you mark one value as the default. A default speeds data entry, but it also means a record can be saved with that value untouched, so pick a default only when it is a safe assumption. Record types complicate both settings, because each record type exposes its own subset of values and its own default, layered on top of the field-level configuration.
Global value sets versus local picklists
A picklist can draw its values from two places. A local picklist stores its values on that one field. A global value set, sometimes called a global picklist value set, stores a shared list once and lets many fields reference it. The setting that connects them is the value set source you choose when you create the field. Global value sets are restricted by definition, so every field that uses one inherits strict enforcement and a single canonical list. Editing the global set updates every field that references it at once, which is the whole point. The tradeoff is scale. If you apply one global value set to more than a handful of objects, Salesforce limits what you can do: past roughly thirteen objects you can deactivate values but can no longer replace or delete them. You can also promote an existing local picklist into a global value set when you realize two objects need the same list. Choosing global early is one of the higher-leverage decisions on a picklist, because it turns "Stage" or "Region" into one definition instead of a dozen drifting copies.
Inactive values and performance limits
Picklist values are never truly gone until you remove them. Deactivating a value hides it from the dropdown but keeps existing records valid, so historical data still reports correctly. Those inactive values accumulate, and Salesforce now caps them to protect performance. A single picklist is limited to a set number of inactive values, and crossing the limit blocks you from deactivating more until you clean up. The "Bulk Manage Picklist Values" tool, now generally available, lets you delete, deactivate, replace, or activate many values at once instead of clicking through them one by one. Replacing a value rewrites it across every record that used it, which is the safe way to merge "In Progress" and "In-Progress" into one. There is a separate cap on controlling picklist values when field dependencies are involved, and dependent picklists have their own combination limits. None of these limits appear until an org has grown messy, which is exactly when they bite, so it is worth pruning inactive values during routine maintenance rather than waiting for an error.
Dependencies between picklists
Picklist Settings extends into how two picklists relate. A field dependency links a controlling field to a dependent field, so the available values in the dependent picklist change based on what the user selected in the controlling one. Pick "North America" in a Region picklist and the Country picklist narrows to only North American countries. The controlling field can be a picklist or a checkbox, and the dependency is defined in a matrix where you map which dependent values are valid for each controlling value. This is a configuration setting, not a validation rule, so it shapes the dropdown itself rather than rejecting input after the fact. Salesforce enforces limits here: a controlling picklist supports up to 300 values, and a dependent picklist allows a large but bounded number of value combinations. Dependencies keep long lists usable and stop nonsensical pairings at the source. They do add maintenance, because every new controlling value needs its dependent mappings filled in, and a missing mapping leaves the dependent field empty for that selection.
Where these settings live in Setup
There is no single screen called "Picklist Settings" that governs every picklist in the org at once. The settings are spread across a few places that together make up picklist configuration. Field-level options, including restriction, default value, and the Reorder screen, sit on the individual field inside Object Manager. Value-set options, including alphabetical sorting and the shared value list, sit on the Picklist Value Sets page under Setup, where global value sets are created and edited. Field dependencies are managed from the object's Fields and Relationships area through the Field Dependencies button. Standard picklists like Lead Status or Opportunity Stage are edited in their own Setup locations and are represented as standard value sets behind the scenes. Knowing which lever lives where saves time, because admins often look for a global toggle that does not exist and miss the per-field control that does. The Metadata API mirrors all of this, exposing GlobalValueSet, CustomValue, and field properties so the same configuration can be version controlled and deployed between sandboxes.
Restrict and clean up a custom picklist
Tightening a picklist so it only accepts approved values is one of the most common data-quality wins. Here is how to restrict a custom picklist and tidy its values in Object Manager.
- Open the field
In Setup, go to Object Manager, choose the object, open Fields and Relationships, and click the picklist field you want to control.
- Enable restriction
Click Edit, then select "Restrict picklist to the values defined in the value set." Save, fixing any non-conforming records the system flags first.
- Order and default the values
Use the Reorder screen to arrange values or turn on alphabetical sorting, and mark one value as the default if a safe default exists.
- Clean up with Bulk Manage
Use Bulk Manage Picklist Values to deactivate stale values or replace duplicates so they merge across existing records in one pass.
Rejects any value not in the active list at save time, across the UI, API, and imports.
Sorts the dropdown alphabetically instead of the manual order you arranged.
Pre-selects one value on new records to speed entry; leave unset when no value is universally safe.
Choose a local list unique to this field or a shared global value set used by many fields.
- Switching a field to restricted fails if existing records hold values outside the set; clean those first.
- New values added under manual ordering do not sort themselves, so reorder them after adding.
- Apply one global value set to more than about thirteen objects and you lose the ability to replace or delete its values.
- Deactivating a value hides it from the dropdown but keeps it valid on records that already use it.
Prefer this walkthrough as its own page? How to Picklist Settings in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Picklist Settings.
- Manage Inactive Picklist ValuesSalesforce
- GlobalValueSet | Metadata API Developer GuideSalesforce
Hands-on resources to go deeper on Picklist Settings.
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 does the Picklist Settings page control across the whole org?
Q2. What is the effect of turning on strict restriction in Picklist Settings?
Q3. Why does the guidance say to configure Picklist Settings deliberately rather than ignore the page?
Discussion
Loading discussion…