Create data sources, fields, and relationships

A data source is the schema-backed collection that Dashier uses to manage a kind of record. The source name is for people; its slug is the stable URL identifier used by the REST API. A well-chosen source describes one coherent concept: Members, Events, Products, or Registrations.

Plan the model before entering fields

Start with the questions the team needs to answer and the records it must change. For a membership directory, a Members source might contain a name, email, join date, and status. An Events source might hold a title, start time, and venue. A Registrations source can refer to both a member and an event. These are illustrative models; choose fields that match your own rules.

Choose field types intentionally

Dashier supports text, textarea, number, decimal, boolean, email, phone, URL, date, datetime, JSON, image, file, enum, reference, array, and rich-text fields. Use an enum for a controlled set of values such as pending, active, and archived. Use a reference when a record should point to a record in another source. Make a field required only when the workflow truly cannot proceed without it; defaults should be explicit and easy to explain.

Each field has a human-readable label and a machine key. The key becomes part of the data shape, so choose predictable labels and avoid renaming a field casually after integrations depend on it. Field options can carry enum choices and reference configuration, including the target source and a display field.

Relationships

A reference field identifies its target source and can describe one-to-one, one-to-many, or many-to-one cardinality. Sketch the relationship first. For example, a Registration may point to one Member and one Event, while each Member can have many Registrations. Dashier’s source and reference controls help operators work with linked records; they do not replace application-specific business rules such as capacity limits or payment state transitions.

After creating a source

Check the generated table and form with sample records. Confirm required values, defaults, enum choices, and reference labels. Then inspect the source’s API path and endpoint policies. Use Managing records, API generation, and Permissions to finish the workflow.