Data tables

Collect the same set of answers over and over, one row per repetition.

Last updated 4 Oct 2026

Overview

A data table asks its questions once, as column headings, and lets the person filling the form in answer them as many times as they need. Use it for anything you cannot count in advance - each person on site, each appliance tested, each room inspected.

A Data Table section selected on the canvas, with its section settings in the right panel

How it differs from a table section

In a table section every field carries its own label on its own row. In a data table the question text appears once, in the column heading, and never again. That is the whole difference, and it is what makes a repeating list readable.

You design one row’s worth of fields - its data elements. Each one becomes a column, and the person filling the form in repeats the row.

What you design                     What comes out
──────────────────────              ────────────────────────────────────────
Name            Text                ┌────────┬───────────────┬──────────┐
Date Of Birth   Date                │ Name   │ Date Of Birth │ Has Pets │
Has Pets        Yes/No              ├────────┼───────────────┼──────────┤
                                    │ Ana    │ 04/11/1988    │ Yes      │
                                    │ Boris  │ 22/07/1975    │ No       │
                                    └────────┴───────────────┴──────────┘

Step by step: build a data table

Add a section to the form.
Set Display on report as to Data Table.
Add a field for each column you want, in the order they should appear.
Give each one a heading - that heading becomes the column heading.
Check the Columns line, which lists the columns as they will come out.
Set Column widths (values out of 100) if the default even split does not suit.

Column headings come from the fields themselves, so renaming a field renames its column. There is no separate list of headings to keep in step.

A field with a child question gets a column for the child as well, immediately after its parent. When the child is hidden on a given row, that cell is simply empty - the grid never skews.

Fixed rows

Sometimes you know the rows in advance: a list of appliances to test, a set of rooms to check. Fill in Rows with a value for each one, and those rows appear on the form already filled in for the first column, so the technician only answers the rest.

Fixed rows are available when the first column is a text, number, date or time field. With any other kind of first column the table stays free-form.

Once you have fixed rows, two more settings appear:

Let the user add extra rows - whether the technician can add rows beyond your list.
Add button text - what that button says. “Add another person” reads better than the default on a register of people.

Choosing which rows reach the report

Rows to include on the report filters what gets printed, based on the answer in a Yes/No, checkbox or multiple choice column. A test sheet can print only the failures, for instance.

Every row is still saved either way. The filter decides what appears on the report, not what is recorded.

Filling one in

On the mobile app and in the Sales portal, each row is its own card with the column headings as labels. The button at the bottom adds another row, and each row can be removed. The report then lays those rows out as a proper table.

Tips

Keep data tables narrow. Five or six columns is about as much as a phone screen handles comfortably.
The ? on the section header brings back the explanation panel if you dismissed it.