> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/hierarchyfilter/configuration/sorting.md).

# Sorting

The items in the hierarchy tree can be sorted alphabetically or based on aggregation. Each level is sorted individually per parent.

To enable this feature, first go to the "Formatting" tab in the "Options" page in the configuration, where you need to select the column/level you want to sort. You can apply sorting on multiple levels.

<figure><img src="/files/QS1AEb1n6SeucHwdsZlS" alt=""><figcaption></figcaption></figure>

After selecting the level you want to sort, scroll down to the "Sort" and "Sort order" fields.

<figure><img src="/files/0yAo7WN7nGgPXcR9XLEj" alt=""><figcaption></figcaption></figure>

Here you can choose between sorting on aggregation or alphabetically. Using aggregation requires an aggregation to be set up. Go to the Aggregation page in this wiki to read more about setting that up.&#x20;

You can select the sort order to choose between ascending or descending. The other options on this page are not necessary to sort the hierarchy. You can click on submit to save these options.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.infotopics.com/hierarchyfilter/configuration/sorting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.