Audience: User
A dataset defines structured content: fields (text, number, choice, date, and more) plus the records authors maintain.
Pages bind lists, labels, and forms to datasets (often via a data source that links the dataset).
| Role | Purpose |
|---|---|
| Content author | Enter and maintain records |
| Project lead | Design schemas that match the business |
Datasets → All — list (name, label, field count)
Datasets → Add — create a schema, or Import CSV
From a dataset row: Records, Edit schema, Edit linked data source (when one exists), Delete
Data → All — browse records across datasets
Data → {dataset} — shortcut to that dataset’s records (up to 25 datasets when present)
Records also open from the dataset’s Records screens (list / add / edit), with filters on indexed fields.
For Fashion Store products / skus, see Variant matrix on the Records page.
📷 Datasets list
Image Path:
images/datasets-list.png
Alt Text:
Datasets list with names and field counts
Caption:
Project datasets.
Products, Events, Team).Expected result: Schema ready for records and page bindings.
See Records.
📷 Dataset records
Image Path:
images/dataset-records.png
Alt Text:
Dataset entry editor with typed fields
Caption:
Editing structured entries in a dataset.
| Action | User | Admin |
|---|---|---|
| View datasets / edit records | Yes | Yes |
| Change schema | Yes | Yes |
| Problem | Cause | Solution |
|---|---|---|
| Page empty | No records / wrong binding | Add records; check field maps |
| Validation errors | Required / type mismatch | Fix field values |
| Schema change breaks UI | Renamed / removed fields | Update page bindings |