> For the complete documentation index, see [llms.txt](https://docs.editable.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editable.io/working-with-editable/explore-data/sort-and-reorder.md). # Sort and reorder EDITable provides standard sorting options to sort the records: ascending/descending as well as A -> Z / Z -> A for numeric and non-numeric columns such as date, numbers, dropdown, text, and more. ## 1. Sort records 1. Hover over the column header you want to sort, then click on the three-dot menu.

2. Select **Sort.** Then, choose **Sort Desc** or **Sort Asc** to sort the records in descending or ascending order respectively. Let's now sort the 'Salary' column in descending order.

3. A downward arrow in the image below indicates that the 'Salary' column is sorted in the descending order.

4. To remove the sort, click on **Remove Sort** as shown. Alternatively, you can click on the sort icon in the column header to remove the sort.

5. Similarly, sorting can also be applied to non-numeric columns. The image below shows the 'Last Name' column sorted in ascending order.

## 2. Reorder columns You can reorder columns by dragging and dropping the headers to arrange them the way you want.

--- # 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.editable.io/working-with-editable/explore-data/sort-and-reorder.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.