> 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/lists-calendars-and-text-search.md).

# Lists, calendars and text search

## Lists, calendars and text search

Backend forms often include dropdown lists, lookup lists, calendars and fields where the user can enter a text fragment.

### Lookup list

If a `...` button is available next to a field, clicking it opens an additional screen with a data list. The user selects the correct row from the list and confirms the selection with `SELECT`, if available.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FTNuqoFilhoAmYm5b3Cvk%2F016.png?alt=media&amp;token=4d094f7d-8af3-46d2-a1cb-d7ab6aa87414" alt=""><figcaption></figcaption></figure>

### Dropdown list

A dropdown list lets the user select one available value. For example, in `Printout type`, the user can select a printout or export format. In this type of field, only values available on the list can be used.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FxBEtjAarSjS33RKtI4PC%2F017.png?alt=media&amp;token=6aef72b2-425e-4124-b5bc-7c26bc7881bc" alt=""><figcaption></figcaption></figure>

### Calendar

A date can be entered manually in `yyyy-mm-dd` format or selected from the calendar available next to the date field. After clicking the calendar icon, the system shows a month view where the user can select a day.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2Fl9QB4yd6Mm77JJw1r6L0%2F018.png?alt=media&amp;token=489e54e8-2ad9-4969-99d1-45ad81a95726" alt=""><figcaption></figcaption></figure>

### Text string search

Some screens allow searching by a text fragment. Depending on the field, operators can be used to define whether the system should search the beginning of text or any fragment:

| Operator | Meaning                                             |
| -------- | --------------------------------------------------- |
| `X*`     | Starts with the specified string, case-sensitive.   |
| `x/X*`   | Starts with the specified string, case-insensitive. |
| `*x/X*`  | Contains the specified string, case-insensitive.    |
| `*X*`    | Contains the specified string, case-sensitive.      |

### What to watch for

* If a field has a dropdown list, select a value from the list instead of entering any text.
* If search returns no results, try a shorter text fragment.
* Enter dates in the format required by the field.

### Related pages

* [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/lists-calendars-and-text-search.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.