A data source is the schema-backed collection Dashier uses to manage one kind of record. Its name helps people; its slug is the stable URL identifier used by the REST API. A good source describes one coherent concept such as 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. A membership directory might have Members with a name, email, join date, and status; Events might have a title, start time, and venue; Registrations can refer to both. These are model patterns, not fixed requirements—choose fields that fit your application.
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 such as pending, active, and archived. Use a reference when a record points to another source. Make a field required only when the operation truly cannot proceed without it, and make defaults explicit.
Each field has a human label and machine key. The key becomes part of the data shape, so avoid casual renames after an integration depends on it. Field options can define enum choices and reference configuration, including the target source and display field.
Let the server own repetitive values
Three field options save manual entry and keep stored data predictable:
- Identifier (id) — read-only and assigned when a record is created. Choose UUID (the default for new sources), an auto-increment number, or a prefixed code such as
MBR-8F3K2Q. Auto-increment numbers can have gaps after deletions. - Auto-generated timestamp (datetime) — filled with the current time on create. Existing values are preserved on edit, and you can still override the value deliberately.
- Reusable option list (enum) — a source keeps a list of stored keys and their displayed labels, so “Nepal” can be stored as
NP. One list can back several fields, and exports contain the keys.
Choose what a reference stores
A reference field has a source key: the target table's value that gets stored in your column. The default is the internal record id, which keeps pointers stable. Point the source key at a target column instead—such as a member number—when external systems should read and send a business key. A separate display label controls what operators see in dropdowns and tables; it does not change what is stored.
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: a Registration may point to one Member and one Event, while each Member can have many Registrations. Dashier’s reference controls help operators work with linked records; they do not enforce capacity, payment state transitions, or other domain rules.
After creating a source
Check the generated table and form with sample records. Confirm required values, defaults, enum choices, reference labels, the API path, and endpoint policies. Use Managing records, API generation, and Permissions to continue.
