> 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/web/table/get-column-number-by-text.md).

# Get Column Number by Text

This is a pre-built Action located under the Table captured from the AUT Element, instructs the Avo Assure to retrieve the column number of the specified text present in the table which is specified in the Input Value and save the result in dynamic variable.

### Syntax

**Input Value**: `<Text>`

| Argument                     | Description                                               |
| ---------------------------- | --------------------------------------------------------- |
| <p>\<Text><br>(Required)</p> | Specify the text of the table column header to be matched |

**Output Value**

| Argument                                 | Description                                                |
| ---------------------------------------- | ---------------------------------------------------------- |
| <p>\<Dynamic Variable><br>(Required)</p> | This dynamic variable holds the extracted column number    |
| <p>\<Dynamic Variable><br>(Optional)</p> | This variable save the result in the **True** or **False** |

**Example**

**Extracts the column number from a table based on the specified column header text**

The **Get Column Number by Text** action takes the value from the Input Value column (e.g., **Requested Date**) and identifies the corresponding column index by searching the column header text in the table. The resulting index is stored in the **{ColumnIndex}** variable and the execution status is saved in the **{Status}** variable with the following possible values:

* **True** – if the column number extracted successfully
* **False** – if the column header is not found or an error occurs

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FEh1GncZsXKLfh7hc0JJ0%2Fimage.png?alt=media&amp;token=f35fe52f-7513-4228-bcb9-7666e1ddd362" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FicR8zhUUxeQ0EHFo5Uec%2Fimage.png?alt=media&amp;token=b34848e5-04d6-4837-9f03-f7b1e00033ec" 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/web/table/get-column-number-by-text.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.