> For the complete documentation index, see [llms.txt](https://datashapes.gitbook.io/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://datashapes.gitbook.io/primer/ui/dropdown-data.md).

# UI.DropDown Data

## 1. Description

This node allows you to create a dropdown input on the UI.MultipleInputForm++ form for the user to select from.

![](/files/-LOD8tMvFnB6YaB9dh8t)

## 2. Inputs

* **InputName (optional):**\
  This input lets you label the dropdown input on the form. All it takes is a string. If no input name is set, the dropdown input will appear wider.

![](/files/-LOD9RGRh87bqbPcdhd1)

* **Keys** and **Values**:\
  These are mandatory inputs, and they work together. The keys are the texts that are displayed to the user in the dropdown menu. This list must mach the list of "Values" so that when a user selects a key in the dropdown menu, the associated value will be returned. In the following example, the keys are the names of the wall types, and the values are the wall type elements.

![](/files/-LODBI3eeMDC6Yp27-g1)

* **DefaultValueIndex (optional):**\
  This input lets you set the value that will be selected by default on the dropdown menu when it is first shown to the user. It takes an integer value that represents the index of the value in the list of values. 

![](/files/-LODCEvboNKhhQfDcA36)

* **Sorted (optional)**:\
  This input is used to determine whether you want your lists of keys/values to be sorted (alphanumerically) or not. It takes a boolean value and is set to *true* by default. If you set it to false, then the items will appear on the dropdown menu in the same order as the Keys/Values lists. 

![](/files/-LODD3ZGeIXeUmLb09Bq)

## 3. Output:

The user input will be returned by UI.MultipleInputForm++ . The object type will be the same as the elements in the "Values" list.

![](/files/-LODDpG66hNkYm5Nd0Ul)


---

# 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://datashapes.gitbook.io/primer/ui/dropdown-data.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.