# Computed Select Fields/Enums

**URL:** <https://community.fibery.io/t/computed-select-fields-enums/7739>\
**Category:** Ideas & Features\
**Created:** [November 5, 2024, 4:39pm UTC](https://community.fibery.io/t/computed-select-fields-enums/7739 "2024-11-05T16:39:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 5, 2024, 6:46pm UTC](https://community.fibery.io/t/computed-select-fields-enums/7739/4 "2024-11-05T18:46:38Z")

</div>

Seems like it is related (the same as?) this topic:

> [@New "Dynamic Single Select" Field Type](https://community.fibery.io/t/new-dynamic-single-select-field-type/3077):
>
> 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: [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: Don’t automatically change the illegal value…

---

_[View the full topic](https://community.fibery.io/t/computed-select-fields-enums/7739)._