Shared Column Properties

These apply to every column regardless of type. Set them in the column's detail panel (select the column header in the builder).

Row Context in Expressions

Inside a column's Value, in any per-row condition (Editable condition, row action Disabled or Visibility), and in blocks placed inside a cell, the current row is available:

Note: Row context pills appear in the expression editor only while the inspector is targeting the table or a block inside it. Outside the table, use {{ id.selectedRow }} instead.

Column Slots

Every column has a Slots area in its detail panel. Drop blocks into a slot to render them as part of that column. Blocks inside a slot read the current row via the row context expressions above.

Column Types Reference

Types marked Editable (required) support inline editing when the column has a Field Key and the table has a Primary Key.

Warning: Type naming gotcha: The calendar-only Date type has id DATE_ONLY; the date-with-time type is DATE. The clock-time type is TIME_ONLY; the duration type is TIME. Use the type id, not the display name, when binding by type in an expression.

Data-Driven (Mapped) Columns

The whole column list can be generated from a data source instead of configured by hand. This is distinct from the Mapped column type — mapped columns decide which columns exist, while the Mapped type changes what one column renders per row.

Switch the table's Columns from a manual list to mapped mode in the table's detail panel, then configure:

Note: Slots in mapped mode are shared, not per column. The one Custom Header template you build is repeated as the header of every generated column — bind {{ tableId.context.currentColumn.<field> }} inside it to vary content per column.

Warning: Exports ignore column visibility in mapped mode — every generated column is exported regardless of its visibility setting.

Behavior & Gotchas

Clicking a column header never sorts

Header-click sorting is turned off by design. Sorting only happens through the toolbar Sort action, which re-runs the data source with the chosen order. The table never sorts rows client-side.

Icon Button fires On Click, not On Click Cell

Every other column type emits On Click Cell when its cell is clicked. The Icon Button column instead emits its own On Click event, because it represents an action rather than a value.

Boolean columns toggle in place

Unlike other editable types, an editable Boolean column does not open an editor overlay. The switch flips directly in the cell, and each flip fires On Change Value and lands in the changeset like any other edit.

Editable toggle requires type + Field Key + Primary Key

The Editable toggle appears only when all three hold: the column type is one of the editable types (Text, Number, Currency, Percent, Date Time, Date, Time, Tag, Boolean, Mapped), the column has a Field Key, and the table has a Primary Key. Fix whichever is missing if the toggle does not appear.

Custom cell values cannot be read from outside the table

All rows render from one configured set of blocks. There is no per-row binding to reach a specific row's inner-block value from outside the table. To capture per-row input (a dropdown choice), use an editable column instead — edits land in the changeset, which the page can read.

Frequently Asked Questions

How do I show a tag whose color changes per row?

Add a Tag column and bind its Value to the row's status field, e.g. {{ orders.context.currentRow.status }}. For automatic coloring, leave Color unset — the same value always gets the same color, assigned deterministically. To color explicitly, bind the column's Color to a condition expression like: {{ orders.context.currentRow.status === 'active' ? 'success' : orders.context.currentRow.status === 'error' ? 'error' : 'neutral' }}.

Why can't I turn on Editable for my column?

Three conditions must all hold: (1) the column's type is one of the editable types (Text, Number, Currency, Percent, Date Time, Date, Time, Tag, Boolean, Mapped), (2) the column has a Field Key set, and (3) the table has a Primary Key configured. Check each in order — the toggle only appears when all three are satisfied.

What is the difference between the Mapped column type and data-driven (mapped) columns?

Three separate things share the word "mapped": the Mapped column type changes what one column renders per row (different row, different renderer). Data-driven columns generate the whole column list from a data source (add/remove columns at runtime). A mapped field on any column picks a per-row value from the row's data. The table's data Source toggle also offers "Mapped" — that refers to where the rows come from.

Can I put a button with different text on each row?

Yes — use a Custom column and drop a Button block into its Custom Cell slot. Bind the Button's label to a row field: {{ orders.context.currentRow.buttonLabel }}. Each row's copy of the cell block renders with that row's data.

I need a column to show different content types per row (a tag in one row, text in another). How?

Use the Mapped column type. Set its Mapped Column Type field to the row field that contains the type id (e.g., columnKind whose values are "TAG" or "TEXT"). The column resolves its real renderer per row from that field's value.

Related Pages