# Computed Select Fields/Enums **URL:** \ **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:** 7\ **Page:** 1
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [November 5, 2024, 4:39pm UTC](https://community.fibery.io/t/computed-select-fields-enums/7739/1 "2024-11-05T16:39:02Z")
A few times this week I found myself wanting to group by something that is related to an existing property. Ex: Group tasks by the due date’s relationship to today (Overdue, Due Today, Tomorrow, Future) or Group tasks for this week by the week day of the due date (in a board view of tasks). At present, I would need to create a formula that returns the value I want to group by. Then create a select field for each if/conditional value. Finally, I would need to use an automation to update the select field to match the value in the formula field when it changes. A similar workaround was mentioned here: > [@Button formula: How to update a single-select field](https://community.fibery.io/t/button-formula-how-to-update-a-single-select-field/2193/1): > > I want to add a button that updates the single-select field with a value calculated by a formula. An ideal experience would be only creating 1 field that is a formula but the results are treated as select values. This way we can group by the options. ---
**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, 4:47pm UTC](https://community.fibery.io/t/computed-select-fields-enums/7739/2 "2024-11-05T16:47:22Z")
The example you mentioned is focussed on date-related grouping. Do you have other use case examples, that are not date-related? The reason I ask is that the ideal experience for your example would not require creating a formula at all, just being able to treat a date field as a select field i.e. add support for grouping (by day, week, month, etc. and optionally as related to the current day, week, month). ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [November 5, 2024, 4:54pm UTC](https://community.fibery.io/t/computed-select-fields-enums/7739/3 "2024-11-05T16:54:00Z")
> [@Chr1sG](#): > > the ideal experience for your example would not require creating a formula at all, just being able to treat a date field as a select field i.e. add support for grouping (by day, week, month, etc. and optionally as related to the current day, week, month. Well that would be amazing! But is a case for more than just dates. A status indicator formula would usually depend on multiple fields. I’m borrowing from a popular strategy used when making task databases in Notion. The formula might take into account the Priority Level field, the Project Type, and due date. - A low priority, overdue task that belongs to internal marketing project may return “Reschedule” - but a high priority task due today that belongs to a client project would return “Top Priority” ---
**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")
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… ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [November 6, 2024, 6:18pm UTC](https://community.fibery.io/t/computed-select-fields-enums/7739/5 "2024-11-06T18:18:34Z")
> [@Chr1sG](#): > > The reason I ask is that the ideal experience for your example would not require creating a formula at all, just being able to treat a date field as a select field i.e. add support for grouping (by day, week, month, etc. and optionally as related to the current day, week, month). This would solve so much for us. We created a very heavy planning solution to achieve this. Since most of our clients are used to Notion or Clickup. And they offer group by date/period. We are currently redesigning this planning module since the amount of mnthly automations may result in an enterprise subscription for small business owners. Which sucks 💩 Is there an ETA for this feature? ---
**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 6, 2024, 6:45pm UTC](https://community.fibery.io/t/computed-select-fields-enums/7739/6 "2024-11-06T18:45:14Z")
> [@YvetteLans](#): > > Is there an ETA for this feature? I’m afraid not. It’s unlikely to happen within 3-6 months if I had to guess ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [February 26, 2025, 4:06pm UTC](https://community.fibery.io/t/computed-select-fields-enums/7739/7 "2025-02-26T16:06:51Z")
It’s related but not the same. I’m on the search for some other info and came across this today I want to be able to use a formula to return a fixed output (say “A”, “B”, and “C”) based on conditions and then use this output the same way a select field is used in the Fibery UI. The Dynamic Select Field feature is about the using Fibery to compute the possible options given other data in the workspace. (Example: select field of all companies labeled as client).