> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/system-basics/adding-editing-and-deleting-records.md).

# Adding, editing and deleting records

## Adding, editing and deleting records

Many backend screens provide buttons used to add, edit, delete, preview or save data. The button set may differ between screens, but their meaning remains consistent.

### Basic operations

| Operation | Meaning                                                                     |
| --------- | --------------------------------------------------------------------------- |
| `ADD`     | Adds a new row or record.                                                   |
| `SAVE`    | Saves data, results or search parameters.                                   |
| `FILTER`  | Filters data according to parameters entered in `Filter`.                   |
| `DELETE`  | Deletes the selected row. The operation must be confirmed or cancelled.     |
| `SHOW`    | Opens the selected row in read-only preview mode.                           |
| `EDIT`    | Opens the selected row for modification. After changes, data must be saved. |
| `Back`    | Returns to the previous screen by one level.                                |

### Typical edit flow

1. Search for data in the table.
2. Select the correct record.
3. Click `EDIT`.
4. Change available fields.
5. Click `SAVE`.
6. Check whether the change is visible on the list.

### Deleting a record

When deleting, the system may display a confirmation message. Confirm the operation only when you are sure that the correct record is selected.

### What to watch for

* Before editing, deleting or previewing, select the correct row.
* Deleting may be unavailable if the record has already been used in the system.
* Not every screen has the same set of buttons.
* After modifying data, changes must be saved.

### Related pages

* [System messages](/aquila-store-user-manual/system-basics/system-messages.md)
* [Filters and data search](/aquila-store-user-manual/system-basics/filters-and-data-search.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aquiladynamics.com/aquila-store-user-manual/system-basics/adding-editing-and-deleting-records.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.