> 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-row-number-by-text.md).

# Get Row Number by Text

This is a pre-built Action located under the Table captured from the AUT element. The functionality of this Action in Avo Assure is to search for the specified text in a table and retrieve the row number where the text is found. The row number is stored in the given dynamic variable for further use during test execution.

## Syntax

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

| Argument           | Description                                  |
| ------------------ | -------------------------------------------- |
| \<Text> (Required) | Provide the text to search for in the table. |

{% hint style="info" %}
**Note**:

* Row numbering starts at 1. The header is counted as row 1, and the first data row is row 2.
* The action ignores letter case when matching text. For example, ABC and abc are treated as a match. However, all characters must match exactly, so ABC and ABC1 are different values.
* If the same text appears in multiple rows, the action returns the first matching row from the top.
* Use a unique value to identify the correct row.
  {% endhint %}

**Output Value**: `<Dynamic Variable>;<Dynamic Variable (Optional)>`

| Argument                       | Description                                              |
| ------------------------------ | -------------------------------------------------------- |
| \<Dynamic Variable> (Required) | Stores the row number where the specified text is found. |
| \<Dynamic Variable> (Optional) | Stores the execution status as `True` or `False`.        |

### Example: Retrieving a Row Number by Text

In this example, the action searches for **Home Improvement Loan** in a table and retrieves the row number of the matching cell.

* **Action**: Get Row Number by Text
* **Input Value**: The Secreate
* **Output Value**: {Row no};{Status}
  * The action searches the table for the specified text and stores the matching row number in the {Row no} dynamic variable.&#x20;
  * The following execution status is stored in the {Status} variable.
    * **True**: The row number is retrieved successfully.
    * **False**: The specified text is not found, or an error occurs during execution.

**Logical Explanation**: The **Get Row Number by Text** action takes the text (For example, The Secreate) from the **Input Value** column and searches for a matching cell in the table. It returns the row number, including the header in the count, and stores the result in the **{Row no}** dynamic variable as **3**. If the optional status variable is provided, the action also stores **True**.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FdtR3n9gepLUmMuZlHrto%2Fimage.png?alt=media&amp;token=763aef5e-36c7-43e1-902c-57c6b5356b35" 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-row-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.
