> 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/sap/dropdown-operations/get-all-key-value-pairs.md).
# Get All Key Value Pairs
This is a pre-built action available under the **Captured Dropdown Element** from the **SAP GUI Application**. The functionality of this action in Avo Assure to fetch the key values for all the items present in the dropdown list and save the result in dynamic variable.
### **Syntax**
**Input Value:** `N/A`
| Argument | Description |
| -------- | -------------- |
| N/A | Not Applicable |
**Output Value:**
| Argument | Description |
| ---------------------------------------- | -------------------------------------------------------------------------------- |
|
\ (Required)
| This dynamic variable holds the all key value pairs retrieved from the dropdown. |
|
\ (Optional)
| This dynamic variable holds the result as **Ture** or **False** |
**Example**
**Fetches all key-value pairs from a dropdown list in the SAP application during execution.**
The **Get All Key Value Pairs** action does not require any input in the Input Value column and retrieves all available key-value pairs from the specified dropdown. The result of the retrieval operation is stored in the **{Pairs}** variable as ( **1000 North Region,** **2000 South Region )**
---
# 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/sap/dropdown-operations/get-all-key-value-pairs.md?ask=&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.
