Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Field Dependency entry
How-to guide

How to set up Field Dependency in Salesforce

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.

By Dipojjal Chakrabarti · Editor, Salesforce DictionaryLast updated Apr 20, 2026

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.

  1. Open Setup → Object Manager → [object] → Fields & Relationships

    Both fields must already exist — the controlling field and the dependent picklist.

  2. Click into the dependent Picklist field

    The field whose values you want to filter.

  3. Click Field Dependencies → New

    Field Dependencies section on the field detail page.

  4. Pick the Controlling Field

    Standard or Custom Picklist, or a Checkbox. Drives which controlling values gate the dependent values.

  5. Click Continue

    Opens the matrix editor — controlling values across the top, dependent values down the side.

  6. 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.

  7. Click Preview to test

    Opens a preview UI showing how the picklist behaves. Verify the filter matches your spec.

  8. Save

    Dependency is committed. Records save going forward enforce the filter; existing records with invalid combinations stay until edited.

Key options
Controlling Fieldremember

Picklist or Checkbox. Multi-select picklists are supported but with limits.

Dependent Picklistremember

Custom Picklist whose values get filtered.

Matrix Editorremember

Per-controlling-value-per-dependent-value inclusion grid.

Gotchas
  • 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).

See the full Field Dependency entry

Field Dependency includes the definition, worked example, deep dive, related terms, and a quiz.