Dependent Field
A Dependent Field is a picklist whose available values dynamically change based on the value selected in a controlling field on the same record.
Definition
A Dependent Field is a picklist whose available values dynamically change based on the value selected in a controlling field on the same record. Dependent fields enforce data consistency by limiting choices to relevant, valid options that correspond to the controlling field selection.
In plain English
“A Dependent Field is a picklist whose available values change based on what's selected in another field called the Controlling Field. The classic example is State depending on Country: pick USA and you see US states, pick Canada and you see Canadian provinces.”
Worked example
Highbridge Insurance's policy-application form has a Region picklist (US, Canada, UK) and a State/Province picklist with 80 entries across all three. Without configuration, the form would show all 80 entries - confusing and error-prone. The admin sets up State/Province as a Dependent Field controlled by Region: when the user picks US, only the 50 US states appear; Canada filters to 13 provinces; UK to 4 nations. Picking the wrong state for the region simply isn't possible - the dropdown won't offer it. Data quality at the source improves; reports filter cleanly because invalid combinations never enter the database.
Why Dependent Field matters
A Dependent Field is a picklist whose available options dynamically change based on the value selected in a controlling field on the same record. The controlling field can be a picklist or a checkbox. Field Dependencies (configured in Setup) define which controlling values map to which dependent values, so when the user picks a controlling value, the dependent picklist filters to show only the valid options for that selection.
Field dependencies create cascading dropdowns that guide users to valid combinations and prevent data entry errors. The classic example is Country (controlling) and State (dependent), but the pattern applies to any hierarchical relationship: product category and subcategory, issue type and sub-type, region and territory. Properly designed dependencies improve data quality dramatically because users literally cannot enter invalid combinations. Multi-level dependencies (where a dependent field is itself the controlling field for another dependent field) can chain several picklists together, though deeper chains become harder to maintain.
How to create Dependent Field
Dependent Fields are picklists whose available values dynamically filter based on a Controlling Field's value — "if Country = USA, show only US states." Configured via Field Dependencies on the dependent picklist. The dependent picklist is the field that gets filtered; the controlling field drives the filtering.
- Make sure the controlling and dependent picklists both exist
Object Manager → object → Fields & Relationships. Both fields must already be created — see custom-field for field creation.
- Open the dependent Picklist field's detail page
Fields & Relationships → click into the dependent picklist. NOT the controlling field — dependencies are configured on the dependent.
- Click Field Dependencies → New
In the Field Dependencies section.
- Pick the Controlling Field
Standard or Custom Picklist (or Checkbox). Drives the filtering.
- Click Continue → matrix editor opens
Controlling values across the top, dependent values down the side.
- For each controlling value: tick which dependent values are allowed
Click cells to include / exclude. Default: all dependent values are allowed.
- Click Preview to test
Opens a preview UI showing how the picklist filters. Verify behavior matches your spec.
- Save
Dependency is committed. Forms now filter the dependent picklist based on the controlling field's value.
Required. Locked after Save.
Required. The field whose values get filtered.
- Dependent Field configuration is on the DEPENDENT field, not the controlling field. Common confusion — devs look for the dependency setting on the controlling field's detail page.
- Field dependencies enforce in UI only. API submissions can write any controlling/dependent combination unless validation rules also enforce — pair with validation for true data integrity.
- Existing records with invalid combinations (where the dependency was added after the data) don't auto-fix. They keep their original values until edited.
How organizations use Dependent Field
Configured a State dependent field controlled by Country, eliminating the cross-country state confusion that used to plague their international users.
Built a three-level dependency chain: Product Category controls Product Family, which controls Product Model. Each selection narrows the next so reps always end up with a valid combination.
Uses dependent fields for Case classification: Issue Type controls Sub-Issue. Picking 'Billing' filters Sub-Issue to billing-related options only, making routing more accurate.
Trust & references
Straight from the source - Salesforce's reference material on Dependent Field.
- Dependent PicklistsSalesforce Help
- Define a Dependent PicklistSalesforce Help
Test your knowledge
Q1. What is a Dependent Field?
Q2. What's a classic example of a controlling and dependent field pair?
Q3. Why use dependent fields?
Discussion
Loading discussion…