> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/dynamic-multi-choice-dmulti.md).

# Dynamic multi-choice (Dmulti)

Let users select several values from a dynamic list built from logic.

Use a **Dynamic multi-choice** field when users should be able to select several values from the same kind of dynamic list.

For the general settings all data fields have in common, see [Shared field settings](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/shared-field-settings.md).

Field-specific settings for **Dynamic multi-choice** are:

#### Everywhere

* **Options logic**: defines the logic that returns the available options

**Display**

* **Name**, **Color**, and **Icon** **logic**: define the label, color, and icon for each option. If you leave these empty, Ninox uses the item's identifier as the label, for example the record ID.

#### On the form

**Display as**: shows the choices as a **Combobox**, **Radio button**, or **Tabs**

{% hint style="info" %}
Use **Dynamic choice** or **Dynamic multi-choice** when the list of options should adjust dynamically to your needs. This is useful when options change often or depend on the current record or user.
{% endhint %}


---

# 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.ninox.com/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables/all-data-fields/dynamic-multi-choice-dmulti.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.