Record Detail Pages and Summary Fields

A table with forty columns is not a portal, it is a spreadsheet with extra steps. But cutting it to six columns loses the other thirty-four, and someone needs those.

Summary fields and detail pages solve both halves: the list shows what you scan by, and the record page shows everything.

What it does

Every table has two field selections:

• Summary fields: what appears on the row in a table, or on the card in a gallery, kanban or calendar view
• The detail page: the full record, opened by clicking the row or card

The same split applies to every view type. On a gallery card it is a cover image and three lines; in a table it is the columns worth scanning. Either way the whole record is one click away.

Why it matters

Choosing summary fields is really choosing what people scan by, and it is the difference between a list someone can use and one they have to read.

A job list where the visible fields are Reference, Site, Date and Status can be scanned in one pass. The same list showing Reference, Created By, Last Modified and Internal ID cannot, even though every column is real data.

Field order runs through everything

Field order is a drag-to-reorder list, set per table (and per role, if you use roles), and it drives every surface at once:

• Table columns and card layouts
• The record detail page
• The create and edit forms, and the sign-up form

Set it once and the portal is consistent everywhere. Fields added in Airtable later land at the end of that order, so nothing you arranged gets rearranged behind you.

How it works

Summary fields are set on the table's Display tab, field order on the Access tab's field list, which also has a name filter for tables with a lot of columns. The summary fields guide covers the split, and record name covers what labels each record.

Who it is for

Any table with more columns than a card can hold, which is most of them: real estate listings, inventory, CRM records, and maintenance jobs.