Structured & Media Fields

Six field types storing a value with more shape than a string or a number: nested data, lists, colours, source code, coordinates, and scannable codes. All share the base field properties.

For the derived and interactive types — formula, count, autonumber, button — see Computed & Action Fields.

json

Stores structured JSON data.

- { id: 5, name: metadata, type: json, required: false }

array

Stores a list of values.

- { id: 6, name: tags, type: array, itemType: string, maxItems: 10 }

Both properties are enforced. itemType is not free text: it is checked against the list below when the config is validated, and an unrecognised spelling is reported by name as a config error. Omitting it stores an untyped list of text.

The accepted spellings, and the PostgreSQL element type each one selects:

Several spellings are aliases for a single type — string and text both select TEXT, so either is correct and the two cannot behave differently. On SQLite an array is stored as JSON text whatever the element type.

color

Stores a colour in hexadecimal format, rendered with a colour picker.

- { id: 7, name: brand_color, type: color, required: true, default: '#3B82F6' }

This is the one field on this page with a real format check: default must match # followed by exactly six hex digits. Three-digit shorthand (#3BF) and named colours (red) are rejected at config decode.

code

Stores source code as plain text, edited with syntax highlighting (CodeMirror 6).

- { id: 8, name: snippet, type: code, language: typescript, lineNumbers: true, tabSize: 2 }

language is required but unconstrained — the listed values are the ones with highlighting support, and an unknown or empty string still passes validation. tabSize has no schema default; the editor falls back to 2 when the field omits it. To render the editor display-only, set readOnly on the form field rather than on the column — read-only is a property of a particular form, not of the stored value.

geolocation

Stores geographic coordinates (latitude and longitude) for location-based features. It takes no type-specific properties beyond the base field properties.

- { id: 9, name: office_location, type: geolocation, required: true }

barcode

Stores a barcode value for product identification and inventory. It belongs to the media category alongside the attachment fields, and is documented here with the other specialised value fields.

- { id: 10, name: product_barcode, type: barcode, required: true, format: EAN-13 }

format is an unconstrained string: it records which symbology the value uses, and nothing checks the value against it.

Related Pages

• Computed & Action Fields — formula, count, autonumber, button.
• Attachment Fields — the other two members of the media category.
• Field Types Overview — every field type by category.
• Tables Overview — the base properties every field shares.
• Table Validation — enforcing shape where the field schema does not.