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.