Fields & Types
Field types, required/defaults, and unique constraints
Fields define the shape of a Data Table — what each record can hold and how it's validated.
Field types
| Type | Use for |
|---|---|
| Text | short strings (names, codes) |
| Long text | notes, descriptions |
| Number | quantities, amounts, scores |
| Boolean | yes/no flags |
| Date / DateTime | dates and timestamps |
| Select | one value from a fixed list |
| Multi-select | several values from a fixed list |
| Email / URL / Phone | validated contact fields |
| JSON | structured/nested data |
| Relation | a link to a record in another table |
Choosing the right type gives you validation, correct sorting/filtering, and the right editor in the UI.
Unique constraints
Mark a field unique to prevent duplicate values. The table then rejects a write that would create a duplicate — whether it comes from the UI, a form, a workflow, the API, or an agent.
Use it to enforce one record per key, for example:
- one row per email in a contacts table
- one row per SKU in an inventory table
- one row per external id when syncing from another system
A rejected write returns a clear error so the caller can handle it (e.g. update the existing record instead of inserting a new one).
Required fields & defaults
Fields can be marked required (writes without them are rejected) and can carry a default value applied when a record is created without one.
Adding and changing fields
Add fields at any time. When you add a field to an existing table, existing records get its default (or empty). Changing a field's type is possible but validate your data first — a type change that doesn't fit existing values can fail.
Next
- Views & Import/Export — filter, sort, and move data in and out.