Record types & fields

The field vocabulary, per-field flags, and how a schema is shaped.

Updated July 26, 2026

On this page

Shape of a schema

A record type has a key (what the SDK calls: dash.records.list("vehicle")), a display name, an icon, a fields list and optional views (table columns, default filters, kanban grouping). Keys are unique per platform.

json

{
  "name": "serial",
  "label": "Serial number",
  "type": "text",
  "required": true,
  "list_visible": true,
  "filterable": false,
  "searchable": false
}

The field vocabulary

Type	Notes
`text`, `longtext`	Single line / rich text.
`number`, `money`	Money is integer cents — never a float, never a pre-formatted string.
`date`, `datetime`	ISO strings.
`select`, `multiselect`, `boolean`	Choice fields carry an `options` list.
`file`, `image`, `signature`	Attachments and drawn signatures.
`url`, `email`, `phone`, `address`	Validated formats.
`customer_ref`, `record_ref`, `user_ref`	Links to a platform customer, another record, or a staff member.
`json`	Structured, app-shaped data with no single input widget — a message thread, a line-item list. Stores cleanly (the data column is already encrypted JSON) but can never be filterable or searchable, because a blob has no scalar to index. Forms skip it: there's nothing for a human to type into.

Record types and the field vocabulary

Shape of a schema

The field vocabulary

Per-field flags