Create, update, and delete records

Once a data source exists, its field definition drives the record form and table. This keeps the operator interface and the API validation aligned: a change to the source schema should be reviewed as a change to both the administrative workflow and the consuming application.

Create a record

Open a source in the project, choose the create action, and complete the generated form. Values are checked against the configured field types; enum fields accept configured options, date fields must parse as dates, and reference fields identify existing records in the target source. Review the resulting row before sharing the API with other systems.

Find and update records

Use the source table to search, sort, filter, and paginate through records. Open a row to edit its values. When an update affects a field consumed by an application, check the application’s assumptions first—for example, an enum value may be rendered as a label, used in a filter, or mapped to a workflow outside Dashier.

For API clients, records can be retrieved at GET /api/v1/{slug}/{id} and updated at PUT /api/v1/{slug}/{id}. Updates are validated and merged against the existing record; the request needs the appropriate endpoint policy and authentication. See the API guide before sending write requests.

Delete carefully

Deletion is available through the interface and DELETE /api/v1/{slug}/{id}. Treat it as a destructive change: verify the selected source and record, confirm downstream references or exports are not needed, and restrict delete permission to roles that need it. Do not assume that application-specific dependencies or external systems are automatically cleaned up.

Keep an operational trail

Dashier includes audit history for changes. Check the activity around important maintenance and use role assignments so the people who can edit or delete data are known. For imports, first preview the rows and validation results rather than using an unreviewed file. See CSV import and Permissions.