Field Dependency
A Field Dependency in Salesforce is a configuration that ties one picklist field''s available values to another picklist''s currently selected value.
Definition
A Field Dependency in Salesforce is a configuration that ties one picklist field''s available values to another picklist''s currently selected value. The controlling picklist determines which values appear in the dependent picklist. A classic example: Lead Source as the controlling field (Web, Phone, Trade Show) drives Lead Subtype as the dependent field (Web restricts to Form, Email, Chat; Phone restricts to Inbound, Outbound; Trade Show restricts to Booth, Demo, Networking).
Field Dependencies are Salesforce''s declarative way to encode if-then logic into picklist UX. Without them, every dependent value would appear regardless of context, and users would pick inappropriate combinations (Trade Show + Form). With them, the platform enforces the relationship: the dependent picklist''s options change as the controlling value changes. The dependency lives as metadata, not as a separate validation rule; it deploys with the picklist fields themselves.
How Field Dependencies work
Controlling field versus dependent field
The relationship is asymmetric. The controlling field drives; the dependent field follows. The controlling field can be a Picklist or a Checkbox; the dependent field must be a Picklist or Multi-Select Picklist. A single controlling field can drive multiple dependent fields; a single dependent field can have only one controlling field.
Configuring the dependency matrix
Field Dependency configuration is a grid: rows are controlling-field values; columns are dependent-field values. You check the dependent values that should be available when each controlling value is selected. The grid is configured in Setup, then Object Manager, then the controlling field, then Field Dependencies, then create new.
Behavior in record forms and Flows
When a user edits a record with field-dependency-bound picklists, changing the controlling field updates the dependent picklist immediately. The dependent picklist filters to available values; previously selected dependent values that no longer match are cleared. Flow Screen components respect the same behavior; the platform synchronizes the values automatically.
Multi-Select Picklists as dependent fields
Multi-Select Picklists can be dependent fields too. The behavior: each selected value on the controlling field opens specific dependent options. If a user changes the controlling value, currently-selected dependent values that are no longer available become invalid; the platform clears them.
Validation rules versus field dependencies
Field Dependencies enforce relationships at the UI level. Validation rules enforce them at the save level. The two complement each other: dependencies prevent users from selecting bad combinations interactively; validation rules catch programmatic writes (API, Apex) that bypass the UI. For critical business rules, use both.
Limitations: standard picklists and master-detail
Field Dependencies have a few limits. Some standard picklists cannot be controlling fields (Industry, Country). Multi-Select Picklists can be controlling but the configuration is more complex. Master-Detail and Lookup relationships cannot be controlling fields. Plan around these constraints during data model design.
Reporting and field-dependency-aware filters
Reports and list views do not automatically filter dependent picklist values based on controlling values. A report filter on Lead Subtype lists all values, not just the ones currently allowed by the controlling Lead Source filter. Users selecting filters from reports must know the business rules; the platform does not enforce them at the report layer.
How to configure a Field Dependency between two picklists
Configuring a Field Dependency takes about 5 minutes. You need both picklist fields already created; then you map which dependent values are available for each controlling value.
- Confirm both picklists exist
The controlling field must be a Picklist or Checkbox already created on the object. The dependent field must be a Picklist or Multi-Select Picklist also already created.
- Open Field Dependencies
Setup, then Object Manager, then the object, then Fields and Relationships, then Field Dependencies. Click New.
- Pick the controlling and dependent fields
Select the controlling picklist and the dependent picklist. Click Continue.
- Edit the dependency grid
The grid shows controlling values as columns and dependent values as rows. Click cells to include or exclude each combination. Use Include Values and Exclude Values for bulk editing.
- Preview and save
Click Preview to see how the dependency will behave in record forms. Adjust as needed. Click Save.
- Test in a record
Edit a test record; change the controlling value. Confirm the dependent picklist''s available options change accordingly. Verify that an invalid combination is no longer selectable.
- Some standard picklists cannot be controlling fields. Industry, Country, and a few others are not eligible; check before designing.
- Dependencies only enforce at the UI level. API writes and Apex code can set any dependent value regardless of controlling field; add validation rules for true enforcement.
- Changing the controlling value clears invalid dependent selections. Users may lose data they entered if they change controlling fields mid-edit.
- Multi-Select dependent picklists have complex behavior. Test thoroughly with multiple selected values across multiple controlling values.
Trust & references
Straight from the source - Salesforce's reference material on Field Dependency.
- Define Dependent PicklistsSalesforce Help
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 a Field Dependency do?
Q2. What field types can serve as controlling fields?
Q3. What's a classic example of a field dependency?
Discussion
Loading discussion…