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.
Real-World Example
a sales rep at Pinnacle Corp recently implemented Field Dependency to manage and organize customer data more effectively. They configure Field Dependency to ensure the sales and service teams have a unified view of every customer interaction, from initial contact through ongoing support. This setup reduces duplicate data entry and improves cross-team collaboration.
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 Organizations Use Field Dependency
- •BrightEdge Solutions — Configured Country as a controlling field and State as a dependent field, eliminating cross-country state confusion in their international customer data.
- •NovaScale — Built a three-level dependency for their product catalog: Category controls Family, Family controls Model. Each selection narrows the options at the next level.
- •Vertex Global — Uses dependencies on Case classification fields so users always pick valid combinations of Issue Type and Sub-Issue.