> 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/working-with-tables.md).

# Working with tables

## Working with tables

A table is most often used in the result section of a screen. It shows data matching search criteria or a list of records available in a module. In many places, further operations such as preview, edit or delete are performed on the currently selected row.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FNGq9PHGa6DMOGmhKJK4v%2F012.png?alt=media&amp;token=f975cc7c-1e46-4179-97ab-4ee80243368a" alt=""><figcaption></figcaption></figure>

### When to use

Use this page to understand how to read search results, select records, use table icons and move between result pages.

### Table elements

| Element          | Description                                                                                                                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Column headers   | Names of data shown in the table, such as `Second name`, `First name`, `Login`, `Role`, `Active`.                                                                                                |
| Rows             | Individual records returned by search or visible in a module.                                                                                                                                    |
| Selected row     | The currently selected record. Further operations, such as preview or edit, are performed on it.                                                                                                 |
| Table actions    | Icons above the table used for additional operations, such as export or column selection.                                                                                                        |
| Position counter | Information below the table showing the visible item range and total result count.                                                                                                               |
| Pagination       | Buttons for moving between result pages when there are more records than fit on one page. Blue buttons are available; grey buttons indicate the current page or a direction that cannot be used. |

### How to work with a table

1. Find the record in the results table.
2. Click the row to select it.
3. Make sure the correct record is selected.
4. Perform the required operation, such as preview, edit, delete, export or open details.
5. If there are more results, use pagination in the lower-right corner of the table.

### Additional details

Some screens may show additional sections below the table or in tabs. These sections usually show details of the selected record and change after another row is selected.

### What to watch for

* Before editing, previewing or deleting, select the correct row.
* If there are many results, check the position counter and pagination below the table.
* Column visibility can be adjusted if the screen supports column selection.
* If a pagination button is grey, it cannot be used at that moment.

### Related pages

* [Sorting and column layout](/aquila-store-user-manual/system-basics/sorting-and-column-layout.md)
* [Adding, editing and deleting records](/aquila-store-user-manual/system-basics/adding-editing-and-deleting-records.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/working-with-tables.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.