> 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/sap/grid-control-operations/get-col-num-by-col-headers.md).
# Get Col Num by Col Headers
This is a pre-built action available under the **Captured Grid Element** from the **SAP GUI Application**. The functionality of this action in Avo Assure is to fetch the column indexes (numbers) that correspond to specific column header names in a Grid object and save the result int he dynamic variable.
### Syntax
**Input Value:** ``
| Argument | Description |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
|
\
(Required)
| Provide one or more column headers separated by semicolon (e.g., Flight Date;Airline) or (e.g., Flight Date) |
**Output Value**
| Argument | Description |
| ---------------------------------------- | ---------------------------------------------------------------- |
|
Dynamic Variable
(Required)
| This variable holds the column indexes by header name |
|
Dynamic Variable
(Optional)
| This dynamic variable holds the result as **True** or **False**. |
**Example**
**Retrieves the column index based on the column header name**
The **GetColNumByColHeaders** action takes the value from the Input Value column **(e.g., Flight Date)** and returns the index position **(e.g., 4)** of the corresponding column in the SAP grid. The result is stored in the **{Col Number}** variable
---
# 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/sap/grid-control-operations/get-col-num-by-col-headers.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.
