> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.7/en/webanwendung/listenansicht/suche.md).

# Search

The search field offers the ability to quickly and effectively search for specific objects such as metrics, reports, or charts. To search the database for these objects, you first enter one or more terms in the search field. The search can then be confirmed either with *Enter* or with the button next to the search field.

As a result, a selection of objects is displayed whose description contains these terms. If no object is found that matches the search query, the message *No data found* appears.

The same filter criteria can be applied in the search as in the [advanced filter](/june5-3.7/en/webanwendung/erweiterter-filter.md).

## Search History

The search history usually works like a Google search. Every confirmed search entry is saved and subsequently offered for selection with each search action. As soon as you type in the search field, the search history is displayed with previously saved search entries that match.

The last ten search entries are always displayed. The search history is updated again with each new entry.

Deleting search entries is done via the corresponding delete button. You also have the option to delete all search entries at once using the "*Clear all*" button.

Saving search history is a global setting and is therefore not assigned to the user.

## Search in Flat List

In a flat list, the entire database is searched for the entered term. Everything that matches the search term is then listed.

## Search in Hierarchical List

In the hierarchical list, the entire database is also searched for the entered term and everything that matches the search term is then listed. In the process, facilities, folders, and views are also displayed that do not match the search term but contain objects with the searched term.

#### Example:

Current Hierarchy: *../View/Pumps*

*-- pump-1*

*-- pump-2*

*-- pump-3*

...

*-- External Pumps (3)*

*-- pump-1*

*-- pump-2*

*-- pump-3*

Enter Search Text: *pump-3*

Result:

*-- pump-3*

*-- External Pumps (1)*

Conclusion:

In this example, the folder *External Pumps* is also listed because it contains an object one level deeper that matches the search term.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.videc.de/june5-3.7/en/webanwendung/listenansicht/suche.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.