Conditional Logic in Dashpivot shows or hides fields in a form based on what a user selects. This article covers what it is, how to use it, and the constraints that apply — including which field types are supported and what happens to data when a condition is no longer met.

Conditional Logic is a Dashpivot feature that shows or hides fields in a form template based on selected field values. It is supported on Yes/No and List fields.

Conditional Logic is used to create dynamic forms that adjust based on user input. It can be used to display follow-up questions, require additional information, or capture supporting details only when specific responses are selected.

Note: Conditional Logic operates on a single layer. Fields revealed by a logic rule cannot themselves trigger additional logic rules.

Use Conditional Logic when some fields are only relevant under certain conditions. For example, teams can display additional questions when a user selects "Yes" to a delay, issue, or variation question in a form. It can also be used alongside workflows to show or hide signature blocks and review panels depending on the current stage of a document.

This video walks through how to set up conditional logic on a site diary template using Yes/No fields. It covers how to add a logic block to a field, set a condition, drag in additional fields, and optionally mark those fields as required.

The following video shows how conditional logic can work in conjunction with:

This video covers how to trigger conditional rules from List fields, how required fields behave when shown or hidden by logic, and how to integrate conditional logic with workflow stages to control the visibility of signature blocks and approval panels.

Only the following field types can trigger conditional logic:

Other field types (e.g. Text, Number, Date, Table, Formula) cannot be used as triggers.

Most field types can be shown or hidden by conditional logic, including Tables and Prefilled Tables. The following are not supported as targets:

Conditional Logic operates on a single layer. A field that is shown by a logic rule cannot itself be set up as a trigger for another logic rule. If you try to add logic to a field inside a logic rule, the option will be disabled.

Conditional Logic is not supported for fields inside a repeating group. Fields inside a repeating group cannot act as triggers and cannot be shown or hidden by a logic rule.

If a trigger field has multiple logic rules, each rule must use a unique trigger value. Two rules on the same field cannot share the same trigger value — the template editor will show a validation error.

When a condition is no longer met and a field becomes hidden, any data entered in that field is cleared. This includes:

This ensures hidden fields do not carry over stale data if the condition changes.

Approval Signatures have their own logic system (sometimes called complementary rules or approval signature logic) that controls when a signature block appears based on AND/OR conditions. This is separate from standard conditional logic and has its own plan-based limits:

This limit applies per signature field, not per template. See How to set up Approval Signature Logic for details.

See how conditional logic is used across common Dashpivot form types:

Which field types support conditional logic in Dashpivot?

Yes/No and List fields can trigger conditional logic. Most other field types — including Tables and Prefilled Tables — can be shown or hidden by a rule, but cannot act as triggers. Page breaks and Approval Signature fields cannot be used as targets.

Can conditional logic be nested in Dashpivot?

No. Conditional logic operates on a single layer. Fields revealed by a logic rule cannot themselves trigger additional logic rules.

Do required fields still apply when hidden by conditional logic?

No. Fields marked as required inside a logic block are only enforced when those fields are visible. If the condition is not met and the fields are hidden, the required rule does not apply.

Does conditional logic work on the Dashpivot mobile app?

Yes. Conditional logic set up in the template builder applies to forms filled out on both the Dashpivot web app and the mobile app.

What happens to data in a field when it is hidden by conditional logic?

The data is cleared. When a condition is no longer met and a field becomes hidden, any data in that field — including table rows and List Property Table Cell values — is removed. This prevents stale data from carrying over if the condition changes.

Can conditional logic be used inside a repeating group?

No. Conditional logic is not supported for fields inside a repeating group. Fields inside a repeating group cannot act as triggers and cannot be targets of a logic rule.