> 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/filters-and-data-search.md).
# Filters and data search
## Filters and data search
The `Filter` section is used to narrow the data list shown in the results table. Not every screen has a filter, but when a filter is available, it is usually located at the top of the workspace.
### When to use
Use filters when the data list is long or when you want to find a specific record, such as a user, product, document, business partner or location.
### Steps
1. Open a screen with a data list.
2. In `Filter`, enter or select the available criteria.
3. If a field has a list or calendar, select a value from the available element.
4. If a field has no list, you can enter a fragment of the searched text. For example, entering `ek` in `Second name` may return all records whose surname contains that fragment.
5. Click `FILTER` or the relevant search button.
6. Check results in `Data`.
### What to watch for
* A filter works according to the parameters entered in `Filter`, such as `Shop`, `Second name`, `Pattern of rights`, `Login` or `Status`.
* Too many criteria may return an empty result list.
* If you cannot find data, remove some filters and search again.
### Related pages
* [Lists, calendars and text search](/aquila-store-user-manual/system-basics/lists-calendars-and-text-search.md)
* [Working with tables](/aquila-store-user-manual/system-basics/working-with-tables.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/filters-and-data-search.md?ask=&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.
