Picklist value deactivation versus deletion
Key Takeaway
To stop users from picking a value but keep it on existing records, deactivate it instead of deleting it.
When a picklist value is no longer needed, an admin can deactivate it or delete it. The choice decides what happens to records that already have the value. Deactivating leaves the value on those records, and you can turn it back on later. Deleting removes the value from those records or swaps it out.
Deactivate versus delete
An active picklist value appears as an option users can pick. An inactive value no longer appears as an option, but it is not fully removed from the org.
| In the picklist | On existing records | |
|---|---|---|
| Deactivate | The value no longer appears as an option. It moves to the Inactive Values section on the picklist's detail page. | Records that held the value when you set it to inactive still contain it. |
| Delete | The value is removed from the picklist. | The value is removed from all records that use it. |
You can bring an inactive value back by clicking "Activate" next to it. Because you can bring a value back, deactivating is a good fit for values you need only part of the time, such as a seasonal product. Deactivating is also a safer alternative to deleting a value entirely.