Adding a value to an existing custom picklist field is one of the most common admin tasks. The steps below add a new active value, place it in the right order, and make sure it shows up for the record types that need it. Always make the change in a sandbox first when a standard field is involved.
- Open the field in Object Manager
In Setup, go to Object Manager, choose the object, open Fields and Relationships, then select the picklist field you want to edit.
- Add the new value
In the Values section (or Values Set for a global set), click New, type one value per line, then save. Salesforce derives the API name from the label.
- Choose record-type assignment
If the field is used by record types, Salesforce asks which record types should include the new value. Select the ones that need it so the option actually appears.
- Set order and default
Use Reorder to place the value in a sensible position, choose alphabetical or manual sorting, and set a default value if this field should pre-fill a common choice.
- Verify and test
Open a record of each affected record type, confirm the value appears in the dropdown, and check that any dependent picklist matrix or validation rule still behaves as expected.
Display the list alphabetically or in a manual order. Use manual order for process stages so they read in real-world sequence.
Pre-select the most common option to cut clicks and steer users toward consistent data entry.
Block users and the API from saving off-list values, which a global value set enforces by nature.
Decide which record types include the new value so it appears for the right teams and not others.
- A new value will not show up if you skip the record-type assignment prompt, even though it exists on the field.
- Renaming a value label is safe, but changing its API name breaks flows, formulas, and integrations that reference the old string.
- Deactivate values you no longer want rather than deleting them, so historical records and reports stay accurate.
- Editing values on a standard picklist like Opportunity Stage can affect forecast categories and closed logic, so test in a sandbox first.