Field Dependency
A Field Dependency in Salesforce is a configuration that filters the available values in a dependent picklist based on the value selected in a controlling field.
Definition
A Field Dependency in Salesforce is a configuration that filters the available values in a dependent picklist based on the value selected in a controlling field. The controlling field can be a standard or custom picklist (or checkbox), and the dependent field is a custom picklist whose options change dynamically. For example, if the controlling field is 'Country' and the dependent field is 'State,' selecting 'United States' would display only US states in the dependent picklist. Field dependencies are configured in the object's field settings under Setup and enforce data consistency without requiring code.
In plain English
“A Field Dependency is a configuration that filters one picklist's options based on what's selected in another picklist. The classic example is Country and State: pick USA and the State picklist filters to US states; pick Canada and it filters to Canadian provinces.”
Worked example
Daffodil Health's intake form has a Region picklist (United States, Canada, United Kingdom) and a State/Province picklist with 80 values across all three countries. Without a Field Dependency, every patient form would show all 80 entries in the State picklist - confusing and error-prone. The admin configures Region as the controlling field and State/Province as the dependent field: when United States is selected, only the 50 US states appear; Canada filters to 13 provinces; United Kingdom to 4 nations. A patient picking the wrong state for their region simply can't - the dropdown won't offer it. Data quality at the source improves, and reports filter cleanly because invalid combinations never enter the database.
Why Field Dependency matters
A Field Dependency in Salesforce filters the available values in a dependent picklist based on the value selected in a controlling field. The controlling field can be a standard or custom picklist or a checkbox; the dependent field is a custom picklist whose options change dynamically based on the controlling value. Field dependencies are configured in Setup under the object's field settings, where admins map each controlling value to the set of valid dependent values.
Field dependencies enforce data consistency without requiring code or validation rules. By limiting what users can pick, the platform prevents invalid combinations like 'France' and 'Texas' from being saved. Common patterns include geographic dependencies (Country/State, Region/Country), product hierarchies (Category/Subcategory/Model), and process dependencies (Status/Sub-Status). Multi-level dependencies are possible by chaining dependent picklists, but more than three levels deep tends to become hard to maintain.
How to set up Field Dependency
Field Dependencies filter a dependent picklist's values based on a controlling field — "if Country = USA, show only US states; if Country = Canada, show only Canadian provinces." Configured per-object, no code required. Enforces data consistency in the UI.
- Open Setup → Object Manager → [object] → Fields & Relationships
Both fields must already exist — the controlling field and the dependent picklist.
- Click into the dependent Picklist field
The field whose values you want to filter.
- Click Field Dependencies → New
Field Dependencies section on the field detail page.
- Pick the Controlling Field
Standard or Custom Picklist, or a Checkbox. Drives which controlling values gate the dependent values.
- Click Continue
Opens the matrix editor — controlling values across the top, dependent values down the side.
- For each controlling value: tick which dependent values are included
Click cells to include / exclude. Default: all dependent values are included for all controlling values.
- Click Preview to test
Opens a preview UI showing how the picklist behaves. Verify the filter matches your spec.
- Save
Dependency is committed. Records save going forward enforce the filter; existing records with invalid combinations stay until edited.
Picklist or Checkbox. Multi-select picklists are supported but with limits.
Custom Picklist whose values get filtered.
Per-controlling-value-per-dependent-value inclusion grid.
- Field Dependencies enforce only in the UI. API submissions can bypass — Apex code or integrations can write any controlling/dependent combination unless validation rules also enforce.
- Existing records with invalid combinations don't auto-fix. Adding a dependency that excludes a previously-valid combo leaves old records in their original state until edited.
- The matrix editor caps at 300 dependent values per controlling value. Larger picklists need to be restructured (split into two picklists, use Record Types instead).
How organizations use Field Dependency
Configured Country as a controlling field and State as a dependent field, eliminating cross-country state confusion in their international customer data.
Built a three-level dependency for their product catalog: Category controls Family, Family controls Model. Each selection narrows the options at the next level.
Uses dependencies on Case classification fields so users always pick valid combinations of Issue Type and Sub-Issue.
Trust & references
Straight from the source - Salesforce's reference material on Field Dependency.
- Dependent PicklistsSalesforce Help
- Define a Dependent PicklistSalesforce Help
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…