Skip to main content
The list view is a collection’s table. A collection with no admin.views has one list view. With other views, the first view in admin.views is the default, of any type, and the list can be first or come later, at /collections/<slug>/<viewSlug>. Its shared properties, such as defaultFields, filter and defaultSort, are in the Collection views reference.

Editing cells in place

A list can let people change a value where they see it, as in a spreadsheet, without opening the record. Turn it on per list view with editable:
These fields edit in the cell:
  • text, textarea, email, number, select, checkbox, date, and single relationship fields.
  • Every field kind from frogbot/fields, such as moneyField and ratingField.
A cell renders the field’s own input, so a custom Field component edits in the cell too. See Fields in list cells. Every other cell keeps opening the record in the record panel: hasMany fields, other field types, the linked first column, and fields the person can’t change. A cell is never editable when any of these is true:
  • The person may not update that record or field.
  • The field, or a group, row, or collapsible around it, is read-only, hidden, or disabled.
  • The field is virtual.
Access is checked for each row with its record, as on the edit page. An access.update that returns a query or reads doc therefore keeps the rows it denies plain. Startup fails on an editable entry that names no field, or one that never edits in a cell: richText, array, blocks, group, tabs, upload, join, autonumberField, and its key field.

Keys

Clicking anywhere else saves a valid change. After an edit, focus returns to the cell.

Saving

A save is one PATCH of that field, so validation, hooks, and access run as on the edit page.
  • An invalid value shows the field’s error in the cell and sends nothing.
  • A failed save shows the error, and the cell keeps what you typed until you fix it or press Esc.
  • In a collection with drafts, a cell saves a draft and never publishes.
  • A saved cell updates its row, and it updates an open record panel that shows the same record.

Summary row

A footer row under the table shows one total per column, across every page of the list, not only the rows on screen. It follows the list’s filters, search and the view’s filter, and counts what the user can read. Set each column’s default with summary, keyed by field path:
count counts the records, whatever the column. Startup fails on a path that isn’t a field, a pairing the field can’t take, or a field that is hidden or has its own access.read: the footer leaves those columns out by design, so they have no total for anyone. Filtering on a field with its own access.read keeps the other columns’ totals for a user its rule allows. Totals use the column’s format: money and percent fields keep their currency and precision, other numbers and counts follow the admin language, and dates use the field’s display format. A column with no value shows nothing, and 0 shows as 0.

Changing a total

Clicking a footer cell opens a menu of the operations its column takes, plus None. The choice is saved for that user and that view with the rest of the view’s setup, so it wins over summary on the next visit, and Reset to default in the view menu returns to the config. summary sets defaults only; it doesn’t lock a column. The footer reads every total with one aggregate request, sent again when the filters, search, columns or choices change, not when the page changes. Totals read each record’s newest draft, the same values its row shows. When rows are grouped, one footer for the whole list follows the last group.