Deleting fields used in picklist dependencies
Key Takeaway
Deleting a picklist dependency and deleting a custom field are different actions. Deleting a dependency removes only the logic and keeps both fields and their data.
A picklist dependency links a dependent picklist to a controlling field, so the dependent picklist's valid values change based on the controlling field's value. Deleting the dependency leaves both fields in place. Deleting a custom field removes the field and its data, and you can't do it if another field references that field.
What a picklist dependency is
A dependent picklist is a custom picklist or multi-select picklist whose valid values depend on another field on the same record, called the controlling field.
For example, a Reason picklist on opportunities can offer Superior features or Lower price only when Stage is Closed Won. Reason is the dependent picklist, and Stage is the controlling field.
Each field type can play only certain roles:
| Field type | Controlling field | Dependent picklist |
|---|---|---|
| Custom picklists | Yes | Yes |
| Standard picklists | Yes | No |
| Checkboxes | Yes | No |
| Multi-select picklists | No | Yes |