> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/grid/verify-table-sort.md).

# Verify Table Sort

This is a pre-built action in Avo Assure. This action checks whether the data in a grid is correctly sorted in ascending or descending order based on a selected column, and saves the result in dynamic variable.

### Syntax

**Input Value:** `<Column Header Value>;<Sort Order>`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>Column Header value<br>(Required)</td><td>Column name from the grid to verified</td><td></td></tr><tr><td>Sort Order<br>(Required)</td><td>ascending or descending order for sorting</td><td></td></tr></tbody></table>

**Output Value:**

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Dynamic Variable>(Optional);&#x3C;Dynamic Variable>(Optional)</td><td>This variable holds the results in <strong>True</strong> and <strong>False</strong></td><td></td></tr></tbody></table>

**Example**

**Verify if a specific column in the table is sorted in descending order**\
\
The **Verify Table Sort** action takes the value from the Input Value column (e.g., **Instrument;descending**) and checks whether the specified column (Instrument) is sorted in descending order. The result is stored in the **{IsSorted}** variable with the following possible values:

* **Ture** – if the column is sorted in descending order
* **False** – if the column is not sorted or an error occurs

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FjYWSOnMWFis3lePqZvSg%2Fimage.png?alt=media&amp;token=2b0ef093-363b-4f4f-a640-28848b75723d" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FFf7caV8A1aYvR66KoYki%2FSort%20Table2.png?alt=media&amp;token=686bc5d9-46a2-4da0-8b6a-f57673ab931f" alt=""><figcaption></figcaption></figure>


---

# 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.avoautomation.com/avo-assure/actions/grid/verify-table-sort.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.