Dependent Custom Fields

Introduction

Dependent custom fields allow you to create field relationships where the options in one field change based on the selection in another. This is especially useful for building structured inputs like Brand → Model → Variant. While powerful, this feature has configuration rules and limitations you should follow for smooth use.

Target Audience

Administrator

Understanding Dependent Custom Fields

Definition

A dependent custom field is a custom field whose values are filtered based on the value selected in another (parent) field. This relationship can be extended across multiple levels (e.g., Brand → Model → Variant).

Key components:

Parent field – usually a dropdown list with single select.
Child field – another dropdown that shows values depending on the parent field selection.
Dependency matrix – defines which child values belong to each parent value.

Note: Dependent fields do not support quick edit mode.

How It Works

Step 1: Set the Parent Field

Create a custom field that will act as the top field in the dependency chain (e.g., Brand).
Format: List
Settings:
- Multi-select: Disabled
- Display type: Dropdown

Step 2: Create the Dependent Field

Create another custom field (e.g., Model).
Add all possible values for all parent selections.
Format: List
Display: Dropdown
In field settings, choose the previously created parent field (e.g., Brand).
Save.

Step 3: Configure the Dependency Matrix

After saving the dependent field, a matrix will appear. Select which values (e.g., Models) should be available for each parent value (e.g., Brands).

Step 4: Add More Levels if Needed

You can continue creating more fields with dependencies. For example, a third field (e.g., Variant) can depend on the second (Model).

Carefully Consider Settings and Changes

Required, hidden, or read-only settings: If a child field is required, the parent field must not be hidden for any role. Ensure visibility and edit settings are aligned across all fields in a dependency chain.
Value changes: If you update values in a parent field, remember to update all related dependent fields and their matrices.
Refresh behavior: When a parent field's value is changed or cleared, the dependent fields update their available values or are cleared accordingly. A page refresh may be required to see the change.
Best practice: Mention all related dependent fields in the parent field’s description to help track dependencies during future updates.

Conclusion

Dependent custom fields offer advanced control over form data and user input by making fields context-aware. They work best when configured carefully with aligned visibility and update rules. By managing dependencies properly, you can build smarter, more structured workflows in Easy8.