Skip to main content

Table Control

The Table control creates a structured grid of rows and columns inside a task. You lay the grid out in the template, deciding which cells are fixed headings and which are left for the user to fill in.

It is the right control whenever the information you need is naturally tabular — inspection scores, inventory counts, meter readings, measurements taken at several points, a signature block for multiple people.

Add to the Template​

The Table control can be added from the controls toolbar in the Template.

Once added you will see a default grid, surrounded by a row of column buttons along the top and a column of row buttons down the left. These buttons exist only in the template editor — they are not shown in the checklist.

Label​

An optional label displayed above the table. Use it to title the table or explain what it is for. Leaving it blank is fine — the table is displayed without a heading.

Adding and Removing Columns​

The buttons above each column let you reshape the grid:

  • Add Column To The Left — inserts a new column to the left of that column.
  • Delete Column — removes that column.
  • Add Column To The Right — inserts a new column to the right of that column.

Adding and Removing Rows​

The buttons to the left of each row do the same for rows:

  • Add Row Above — inserts a new row above that row.
  • Delete Row — removes that row.
  • Add Row Below — inserts a new row below that row.

Static Cells vs. Editable Cells​

This is the key idea in the Table control, and it is controlled purely by whether you type something into the cell in the template:

  • Enter a value into a cell in the template and it becomes static — the text is fixed and read-only in the checklist. This is how you build column headers and row labels.
  • Leave a cell empty in the template and it stays editable in the checklist, for the user to type into.

There is no separate read-only switch: the presence of a value is the switch. A reminder of this is displayed underneath the table in the template editor.

Cell Settings​

Each cell has a small dropdown arrow on its right-hand side. Opening it gives you two settings:

  • Background — apply a background colour to the cell to aid visual categorisation. The choices are Red, Orange, Yellow, Green, Blue, Grey and White (the default). Colour is commonly used to group related columns, or to mark a row that needs particular attention.
  • Is Required? — the cell must have a value entered before the parent task can be completed. Only meaningful on editable cells; a tick is shown against the option when it is enabled.

Allow Add/Remove Rows in Checklist​

Tick Allow Add/Remove Rows in Checklist, beneath the table, to let users add and remove rows while running the checklist. Use it when you do not know in advance how many rows will be needed — a list of defects found, or attendees at a meeting.

With this option enabled, users see the same Add Row Above / Add Row Below / Delete Row buttons down the left of the table that you use in the template. Delete is only offered on rows that contain at least one editable cell, so a fixed header row cannot be removed.

Populating from a Data Set​

A Table can be filled from a Data Set, giving each checklist one row per record — one row per site, asset or employee — without anyone having to type them in.

Choose Link to Data Set from the control's settings cog, then map each column to either a Data Set field or — User-entered —:

  • Mapped columns are filled from the Data Set and are read-only in the checklist. Their headers become the field names.
  • User-entered columns stay blank and editable, for the person running the checklist to fill in.

The rows are captured when the checklist is created, and the linked View must return 500 records or fewer. If Allow Add/Remove Rows in Checklist is enabled, users can still add their own extra rows; rows that came from the Data Set cannot be deleted, because none of their mapped cells are editable.

See Linking a Data Set to a Control for the full walkthrough.

Use in the Checklist​

The table is displayed as a grid, with the label above it if one was set.

Static cells show their fixed text and cannot be changed. Editable cells are shown as input boxes that the user can click and type into. Values are saved as they are entered, and the control records who last changed it and when.

If Allow Add/Remove Rows was enabled, the row buttons are displayed down the left-hand side.

Validation​

If any cells are marked as Is Required?, validation is performed when the user completes the task. The task cannot be completed until every required cell has a value.

Cells that fail validation are outlined in red, and the message "Please enter a value in the cells with a red border" is displayed beneath the table.

note

Required-cell validation is applied when the task is completed from within the checklist. Unlike the other input controls, it is not currently enforced when a task is completed from elsewhere — for example from the Dashboard or through the API. If it is essential that a value is captured, back the table up with a required Short Text or Sub-Tasks confirmation.

Conditional Logic​

A Table cannot be the source of a Conditional Logic rule — you cannot branch on what a user typed into a cell.

It can be the target of a rule, so a whole Table can be shown or hidden by a condition driven by another control. A common pattern is a Dropdown selecting the type of inspection, which reveals the table of readings that applies to it.

Dynamic Values and Parameters​

Table content is available as a Dynamic Value, so the data entered into a table can be pulled into a Text control or a Mail-To email elsewhere in the same checklist. The whole grid is inserted as a table, and it refreshes as cells are filled in — which makes it a neat way to include a completed set of readings in an automatically sent email.

The Table control itself does not accept dynamic values or Template Parameters — cell contents are set in the template or by the user, or supplied by a linked Data Set.

Linked Checklists​

A Table cannot take part in a Linked Checklist control mapping, as either the parent or the child side.

Reporting​

The Table control is not available as a column in Reports. A table holds a grid of values rather than a single answer, so there is nothing meaningful to place in a single report cell.

If you need the values in a table to be reportable, capture the important ones in individual Short Text, Drop-Down or Date controls instead. Table data is still visible in the checklist itself and in the checklist's print view.

Limits​

LimitValue
Records from a linked Data Set View500, and only when pre-populate rows is enabled. Without it there is no cap beyond the 10,000 record limit per Data Set.
Cell background colours7 — Red, Orange, Yellow, Green, Blue, Grey and White (the default)
Rows and columnsNo limit
Cell content lengthNo limit

Notes and Limitations​

Last updated on