> 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-value-in-table.md).

# Verify Value in Table

This is a pre-built Action located under the captured **Grid Element**. The functionality of this Action in Avo Assure is to verify whether the specified value is present in the grid and store the verification result in a dynamic variable.

## Syntax

**Input Value**: `<Value to be verified>`

| Argument                                        | Description                                    |
| ----------------------------------------------- | ---------------------------------------------- |
| <p>\<Value to be verified></p><p>(Required)</p> | Provide the value to verify in the grid table. |

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

| Argument                                                     | Description                                                                                                                               |
| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| \<Dynamic Variable>(Optional); \<Dynamic Variable>(Optional) | Both dynamic variables Stores the verification result as **True** or **False** based on whether the specified value is found in the grid. |

### Example: Verifying a Value in a Table

In this example, we explain how to verify whether a specific value exists in a grid.

* **Action**: Verify Value in Table
* **Input Value**: Tony Smith
  * The input value (**Tony Smith**) specifies the data that needs to be verified within the Grid.
* **Output Value**: {Status}
  * 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 **Verify Value** in Table action takes the value from the Input Value column (**Tony Smith**) and searches the identified table for the specified value. The action stores **True** in the **{Status}** variable.

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F5dRPgnoHOLpl2o3hw8Ps%2Funknown.png?alt=media&amp;token=5ef7847a-d323-43e5-ad7c-8e85812c079b" alt="" height="43" width="562">

#### Knowledge Bites

Here are some examples of the different value verification:

| Scenario                       | Input Value | Result                                                       |
| ------------------------------ | ----------- | ------------------------------------------------------------ |
| Verify employee name in a Grid | John Smith  | Returns **True**, if the employee name exists in the Grid .  |
| Verify order ID in a grid      | ORD12345    | Returns **True**, if the order ID is found in the table.     |
| Verify unavailable data        | ABC999      | Returns **False**, if the value does not exist in the table. |


---

# 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-value-in-table.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.