> 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/dropdown/select-by-value.md).

# Select by value

This is a pre-built Action located under the captured dropdown element. The functionality of this action in Avo Assure is to select a value from the dropdown based on the input provided. The result is stored in the given dynamic variable for further use during test execution.

## **Syntax**

**Input Value**: `<value>`

| Argument                      | Description                                                                                                                                                       |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<value><br>(Required)</p> | <p>Provide the value which you wants to select from the dropdown or list.</p><p>Supported input format:</p><ul><li>Numeric</li><li>Text</li><li>Dynamic</li></ul> |

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

| Argument                                                    | Description                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | Both dynamic variable stores the status as **True** or **False**. |

### **Example: Selecting an Option from a Dropdown using a Numeric Value**

In this example, we explain how to select a specific option from a dropdown based on the numeric value provided.

* **Action**: Select By Value
* **Input Value**: 2
  * The first argument (**2**) specifies the numerical value representing the option to be selected from the dropdown.
* **Output Value**: {Status}
  * The result of the selection operation is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the value is selected successfully.
    * **False**: If the value is not selected successfully.
* **Logical Explanation**: The **Select By Value** action takes the value from the **Input Value** column (**2**). It identifies the corresponding option in the captured dropdown element and performs the selection. After the option is selected, the action stores the result (**True**) in the **{Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FuXXL1XuZY2FxmY0Fpmkg%2Fimage.png?alt=media&amp;token=3f27d106-e4de-4599-8b76-2f78b0090ecc" 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/dropdown/select-by-value.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.