> 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/custom/verifycount.md).

# verifyCount

This is pre-built Action located under the **@Custom Element.** The functionality of this action in Avo Assure to verify the user-provided input count with the total number of options present in the dropdown or list and store the result in dynamic variable.

### **Syntax**

**Input Value:**`<ObjectType>;<VisibleText(optional)>;<Index>;<Count>;<abs(optional)>`

| Argument                            | Description                                                                                                    |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| <p>\<ObjectType><br>(Required)</p>  | Specify the type of object (e.g., Select, Dropdown, list)                                                      |
| <p>\<VisibleText><br>(Optional)</p> | Enter the visible text on the object                                                                           |
| <p>\<Index><br>(Required)</p>       | Provide the index of the object inside the page                                                                |
| <p>\<Count><br>(Required)</p>       | Expected number of items/options in the dropdown or list                                                       |
| <p>\<abs></p><p>(Optional)</p>      | If the **abs** is provided, the action is performed with absolute identification using the **absolute X path** |

{% hint style="warning" %}
**Note:**\
If the abs argument is specified, then the action will be executed with absolute performance based on the given visible text.

*To skip an optional input value, use an extra semicolon (;).*
{% endhint %}

**Output Value**

| Argument                                                    | Description                                                            |
| ----------------------------------------------------------- | ---------------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This dynamic variable holds the action result in **True** or **False** |

**Example**

**Validates the number of elements present in the specified object against the expected count**

The **Verify Count** action takes the value from the Input Value column (e.g., **select;;0;4**) and verifies whether the number of items in the specified object matches the expected count. The result of the verification is stored in the **{Verify}** variable, with the following possible values:

* **True** – if the count matches the expected value.
* **False** – if the count does not match

<figure><img src="/files/MFT45zTkFhoDvCI3giwX" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/actions/web/custom/verifycount.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.