Dependent Lists

Dependent Lists are not a list type, but rather a configuration pattern that creates a relationship between fields: the selection made in one field automatically determines which options are displayed in another field.

This behavior works with any combination of list types — default with default, default with nested, or nested with nested.

How it works

The mechanism relies on the Reference field of lists. To configure dependent lists, you need:

1. A main list — linked to the first field (e.g.: "Responsible Area"). The options in this list have defined values.
2. A list for each option — linked to the second field (e.g.: "Service"). Each of these lists must have in the Reference field the exact value of the corresponding option in the main list.

When the user selects an option in the first field, the second field automatically loads the list whose reference matches the selected value.

Practical example

Imagine two fields in a service request category: Responsible Area and Service.

Step 1 — Create the main list: A list called "Areas" with the options: Administration, Accounting, Business Development.

Step 2 — Create a list for each area:

• List with reference Administration → options: Processing Fees, Reimbursement, Retention Fee, Service Address, General.
• List with reference Bookkeeping → options: Monthly Report, Annual Statement, Payroll.
• List with reference Business Development → options: Prospecting, Commercial Proposal, Follow-up.

Step 3 — Link to the fields: The "Responsible Area" field uses the "Areas" list. The "Service" field is configured with the multiple lists created in step 2.

Result: When selecting "Administration" in the "Responsible Area" field, the "Service" field will automatically display the options Processing Fees, Reimbursement, Retention Fee, Service Address, and General.

Important notes

• The dependent list's Reference value must match exactly the option value in the main list. Any spelling difference will prevent it from working.
• You can combine different types: the main list can be nested and the dependent ones default, or vice versa.
• The number of dependent lists is unlimited — you can create as many as needed to cover all options in the main list.