Table - Blue Docs

A Table custom field holds a small grid of rows and columns inside a single record. You define the columns once — each with its own type — and then add as many rows as the record needs: the line items on an invoice, the rounds of an interview, the parts on a work order.

It’s the answer to “this record needs a list of structured things” without spinning up a whole separate workspace of linked records. Each column holds one kind of value, and Blue gives you the right input for it — a date column opens a date picker, a select column only lets you pick from your options, a currency column formats the money — so the data stays clean instead of being a grid of free text.

Defining columns

A Table field is configured by its columns. When you create the field you add up to 10 columns, give each a name and a type, and arrange their order. Columns are matched to their stored values by a stable internal id, so renaming or reordering a column never rewrites the data already in your rows.

Column types

Each column is one of the following types:

Type	What it holds
Text	Free text, up to 2,000 characters per cell.
Number	A numeric value, with optional decimal precision, prefix, and min/max.
Date	A calendar date, chosen from a date picker.
Checkbox	A simple checked / unchecked toggle.
Single select	One choice from a list of coloured options you define.
Multi select	Any number of choices from your list of options.
Currency	A money amount in a currency you allow.
Formula	A value calculated from the other columns in the same row (read-only).

Formulas

A Formula column computes its value from the other columns in the same row. Reference another column by name in the expression — multiply a Quantity by a Unit price to fill in an Amount, add two figures together, apply a rate, and so on.

The result can be a plain number or a currency.
Formula cells are read-only and recalculate automatically as the other cells in the row change.
A formula can build on another formula column, so you can layer a subtotal into a total.

Column totals

Any column can carry a total that appears in a footer row beneath the table:

SUM adds up a Number, Currency, or Formula column. Currency columns are summed per currency, so unlike amounts are never silently added together.
COUNT reports how many rows have a value in that column.

This puts the number that matters — the invoice total, the count of items — right on the record.

Unique columns

A Text, Number, Date, Currency, or Single select column can be marked unique, which requires every row in that record to hold a different value for it — handy for things like a line-number or SKU column where duplicates would be a mistake.

Examples

Invoice or quote line items — Item, Quantity, Unit price, and a Formula Amount column, with the Amount summed into a total at the bottom.
Interview scorecard — one row per round, with the interviewer, a coloured rating, an “advance” checkbox, and a date.
Order or packing list — each item with a quantity and a checkbox to tick off as it’s packed.
Budget breakdown — a row per line, summed for the whole record.
Measurements or readings — a structured set of values captured against one record.

When to use a Table vs linked records

A Table is best for a small, self-contained list that belongs to one record and that you read alongside it. If you find yourself wanting to filter, group, or report on those rows across many records — or you’re pushing past the size limits below — that data is better off as its own workspace, connected with Reference, Lookup, and Rollup fields instead.

Limits

Up to 10 columns and 100 rows per record.
Up to 2,000 characters per text cell.