Typed fields, not free text
Text, boolean, integer, number, date and time, coordinates, list and reference — each with its own rules, checked on every console and API write.
Rename the label, keep the id
A field’s display name can change whenever you like; the reference id that bindings, forms and imports use never moves. Descriptions show as hints.
Shared with the sites you pick
Datasets belong to the organization, so a collection can drive pages on any site it is shared with, and the server enforces that sharing.
References and many-to-many
Point a field at another dataset’s records, allow multiple for many-to-many, or create a join collection that pairs two. A delete checks what still points at it.
Forms, workflows and the API
A bound form, a workflow action and the /v1 API write the same rows as the record editor — by id, so renaming a dataset never breaks a binding.
CSV and JSON, both directions
Export streams the whole collection and refuses a short file. Import matches columns by id or display name and validates every row on the way in.