> 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/get-row-data.md).

# Get Row Data

This is a pre-built Action located under the captured **Grid Element**. The functionality of this Action in Avo Assure is to retrieve data from a specified row in the grid based on the row value or row index provided in the input value and store the retrieved row data in a dynamic variable for further use during test execution.

## Syntax

**Input Value**: `<Row Value> or <index; Row Index>`

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

* Ensure that the specified value or row index exists within the grid before executing the action.
* Use either `<Row Value>` or `<index; Row Index>` as the input value to identify the required row.
  {% endhint %}

| Argument                                                         | Description                                                                  |
| ---------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| <p>\<Row Value><br>(Required)</p>                                | Provide the value of the row to identify the required row.                   |
| <p>\<index; Row Index></p><p>(Required when using row index)</p> | Provide index followed by the row index to identify the row by its position. |

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

| Argument                      | Description                                                                  |
| ----------------------------- | ---------------------------------------------------------------------------- |
| \<Dynamic Variable>(Optional) | This dynamic variable stores the retrieved data from the specified grid row. |
| \<Dynamic Variable>(Optional) | This dynamic variable stores the execution status as True or False.          |

#### Example: Retrieving Grid Row Data Using a Row Value

In this example, we explain how to retrieve data from a grid row by specifying a value present in that row .

* **Action**: Get Row Data
* **Input Value**: Tony Smith
  * The input value (**Tony Smith**) represents a value available in the target grid row.
  * Avo Assure searches the grid for this value and retrieves the complete data associated with that row.
* **Output Value**: {Row Data};{Status}
  * The dynamic variable **{Row Data}** stores all data retrieved from the matching grid row.
  * The execution result is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the specified value is present in the grid.
    * **False**: If the specified value is not present in the grid.
* **Logical Explanation**: The **Get Row Data** action takes the value from the **Input Value** column (**Tony Smith**) and searches the grid for the matching row. The action retrieves all data from the matching row and stores it in the **{RowData}** variable. The execution result is stored in the **{Status}** variable as **True**.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FuVjkiYOv4fb5SboyhYTj%2Funknown.png?alt=media&amp;token=c9e39157-1ebb-4133-8631-5df702ba33a3" alt="" height="47" width="626">


---

# 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/get-row-data.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.