> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/assets/searching-and-sorting-asset-items-within-a-group.md).

# Searching and sorting assets within a group

When an asset group holds many assets, the search and sort tools help you find the one you want. A search icon at the top-right of the **Assets** section expands into a text field when you click it; what you type matches against an asset's attribute values, all of them combined, so you can type a model number, size, location, or serial number and it filters to assets whose attributes contain what you typed.

Multiple words act as an AND search: every word you enter must appear somewhere in the asset's attributes for it to stay in the list. The match ignores spacing, so partial fragments still work.

To order the list, click a column header to sort by that attribute, and click again to reverse the direction. Your sort choice is remembered per asset type, so it stays put when you come back.

The **#** column keeps each asset's own position number, so searching or sorting never renumbers anything — a filtered list shows the numbers it kept (1, 2, 4, 5 …) with gaps where the hidden assets sit. That way a number always identifies the same asset, whatever is on screen.

Note that while a search or a column sort is active, the manual Reorder option is turned off, since both change which rows are shown and in what order. Sorting by **#** in ascending order is the exception: it restores the group's own order, so Reorder stays available. (Sorting **#** descending does not, since that reverses the list.) The table also includes a column for each recurring service that applies to the type, labeled "\[Service] Due".

These show each asset's soonest next due date for that service, or a dash if none applies, letting you sort or scan by what's coming up next. Search and sort affect only the assets on screen; they never change or delete anything.

> **Where to find it:** On an asset group page, the search icon at the top-right of the **Assets** section. Click a column header in the table to sort. ***\[Service]***** Due** columns show each asset's next due date.

## Related guides

* [Editing, reordering, and deleting assets](/field-operations/assets/editing-reordering-and-deleting-asset-items.md)
* [Asset groups and assets: terminology and screen labels](/field-operations/assets/assets-vs-asset-groups-vs-asset-items-the-terminology.md)
* [See and browse all your asset groups (the Asset Groups page)](/field-operations/assets/see-and-browse-all-your-asset-groups-the-assets-page.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://learn.withessential.com/field-operations/assets/searching-and-sorting-asset-items-within-a-group.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.