Table Field: Structured Rows in a Form

Some data doesn't fit a single input. A list of dependents, an income breakdown by source, a schedule of properties — each needs its own columns, its own row count, and its own rules. The new Table field lets managers design a mini-spreadsheet inline in a template: name the columns, pick a type for each, and clients fill in the rows. AI extraction understands the structure, and the data comes out the other side as clean, typed rows.

What's New

Table as a first-class field type

The builder palette now includes Table alongside Text, Number, List, and the rest. Adding one creates a default single-column text table that you can expand in place.

Column management in the builder

Each column has a name, a type (text, email, number, or currency), and an optional required flag. Columns can be added, removed, or reordered from the field's configuration panel. Currency columns accept a per-column prefix, the same way standalone currency fields do.

Row controls on the client side

On the portal form, clients see a table with a header row and typed inputs in each cell. Add Row and Remove Row controls let them grow or shrink the data to fit what they actually have. Min and max row counts enforce expectations — require at least two dependents, cap a schedule at ten entries.

AI extraction knows the columns

When AI reads an uploaded document, the extraction prompt now describes the table's column structure so the model can return an array of objects matching it. Uploaded tax schedules, income statements, and beneficiary lists flow straight into the table's rows without manual rekeying.

Rendered in folio detail

Table values render as a proper table in the folio detail view, with the configured column names as headers. Exports and downstream integrations receive a clean array of typed objects per row.

How to Use It

Open a template in the Builder
Drop a Table field into a section
Name it, set min/max rows, and add the columns you need
Pick a type for each column (text, email, number, or currency) and mark required columns
Save and publish the template
Collect — clients fill rows, AI pre-fills from uploaded docs, you review in folio detail

What's Improved

Consolidated field rules

List and table fields now share the same state-required / style-hint / style-options machinery as the rest of the field types, so the behaviour and configuration UI is consistent no matter which field you're working with.

List Field — Variable-length single-column input that shipped alongside table