Conditional visibility
Show or hide fields based on other answers, list columns, and comparison operators.
Video coming soon
Conditional visibility
id: academy-conditional-visibility · ~2–4 min
Describe the follow-up
Audience: Admin
Conditional visibility lets you show a field only when another answer matches a rule. Hidden fields are skipped on mobile and are not required while hidden. Rules are stored as Show only when… on each field (visibleWhen in the form definition).
Where to configure rules
Select a field on the Form Builder canvas and open Visibility Rules in the right panel—or use the Field visibility logic view to see which fields depend on others. Conditions control field visibility only; they do not route users between wizard steps.
Worked example
Suppose field A asks Issue type with options Leak, Electrical, and Other. Field B (Pipe diameter) should appear only when A equals Leak.
- Add both fields; place A above B in form order.
- Select B and add a visibility rule: source A, operator is, value
Leak. - Preview on mobile: choose
Electrical—B stays hidden. ChooseLeak—B appears and can be marked required.
Add more rules on other fields the same way—for example show Other details when A is not Electrical.
Operators
| Operator | Typical use |
|---|---|
| is | Exact match (text, number, date, yes/no) |
| is not | Hide unless the answer differs |
| is one of | Match any value in a list |
| is none of | Hide when answer is in a list |
| has any value | Show when the source was answered |
| is empty | Show when the source is blank |
| is not empty | Show once the source has data |
| is greater than / is less than | Numeric comparisons only |
Pick an operator that matches the source field type. Numeric comparisons require a number source.
Sources: form fields and list columns
The Source can be:
- Any earlier form field (text, number, date, radio, checkboxes, list selection, etc.).
- A column from a List field bound to a Data Source—for example show
Warranty noteswhen@equipment.categoryis one ofPremium,Extended.
List-column sources read the value from the row the user selected. If the list is cleared, dependent fields hide again.
Behavior at runtime
Rules re-evaluate as the user types or changes selections. Clearing the controlling answer hides dependent fields and clears their validation state. Put controlling questions above the fields they unlock so the flow reads naturally on mobile.
Tips
- Keep chains shallow—one or two hops (
A → B → C)—so testers can predict what appears. - Do not mark a hidden field as required unless it can become visible in the same visit.
- When renaming field slugs, reopen visibility rules to confirm sources still resolve.
- Combine with Lists from Data Sources to drive visibility from catalog columns.