# New "Dynamic Single Select" Field Type

**URL:** <https://community.fibery.io/t/new-dynamic-single-select-field-type/3077>\
**Category:** Ideas & Features\
**Created:** [July 15, 2022, 6:29pm UTC](https://community.fibery.io/t/new-dynamic-single-select-field-type/3077 "2022-07-15T18:29:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [July 15, 2022, 6:29pm UTC](https://community.fibery.io/t/new-dynamic-single-select-field-type/3077/1 "2022-07-15T18:29:52Z")

</div>

I’d like to see a new Single Select field type that uses a Formula to filter or create the choices presented in the UI on a per-entity basis.

Such a formula might be as simple as:

```auto
[DB_of_all_Possible_Options].Filter(Type = SelectedType)

```

I’m aware that there’s the question of what to do when a previously selected option becomes “illegal”, but this same problem exists when a Rule or Formula references a deleted field.

For this situation I suggest:

1. Don’t automatically change the illegal value, but display the field in a distinctive way to flag the condition.
2. Allow the condition of an illegal value to be detected by a Rule, so it can be addressed by automation.

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [July 16, 2022, 8:11pm UTC](https://community.fibery.io/t/new-dynamic-single-select-field-type/3077/2 "2022-07-16T20:11:19Z")

</div>

Related:

> [@Dependent Dropdown Field Type](https://community.fibery.io/t/dependent-dropdown-field-type/647):
>
> Hi Guys, Sorry if this is a detailed request, but I’ve seen a lot of times I could use a “Dependent Dropdown” capability with fields in Entities. What I mean is if I have one dropdown that I’m using, the options would lead to a 2nd related dropdown that would have dependent results based on the choice of the first: Let’s say we want to categorize a “Recipe” Entity type: First Dropdown: “Food” Choices: Meat Vegetable Fruit Values in 2nd Dropdown: Beef Pork Spinach Lettuce Broccoli Appl…
