> 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/supertables/features/sorting-columns.md).
# Sorting Columns
Click on a header to sort the rows in an **ascending** order. Click again for a **descending** order, a further click will bring you back to the **original sorting order**. You can also select a **secondary sorting column**, just hold the **Shift** key while clicking the second column header. For example, your first sorting is on “Product Category” and the second sorting is on “Customer Segment”. When using multiple columns for sorting, you will see a small integer appear in the column header to indicate the first, second, third etc. columns you sorted the data on.
Sorting columns
Set a **default sort order** for dimensions, or set a **custom sort order**, overwriting the default alphabetical order:
---
# 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.infotopics.com/supertables/features/sorting-columns.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.
