# Dependent Dropdown Field Type

**URL:** <https://community.fibery.io/t/dependent-dropdown-field-type/647>\
**Category:** Ideas & Features\
**Created:** [April 18, 2020, 9:55pm UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647 "2020-04-18T21:55:19Z")\
**Posts on this page:** 8\
**Page:** 2

<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:** [June 14, 2023, 1:21pm UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647/21 "2023-06-14T13:21:57Z")

</div>

This is quite a long topic with many replies, but I’d be interested to know if the relation filters that were released recently can solve some/most/all of the use case?

> [@April 6, 2023 / Relation filters, breadcrumbs in search, back-references in Documents](https://community.fibery.io/t/april-6-2023-relation-filters-breadcrumbs-in-search-back-references-in-documents/4266):
>
> raised_hand Relation filters Instead of sifting through an entire Database when linking one Entity to another, pre-filter the options: exclude done and archived work (ex. don’t suggest long-forgotten Projects for a Task) remove irrelevant stuff (ex. stop suggesting sales reps when assigning people to a Bug) ensure a proper process (ex. make it harder to add Stories to an already full Sprint) It takes one Fibery guru (yourself!) to configure the relation filters — and everyone…

> [@April 21, 2023 / Breadcrumbs on Views, strict relation filters](https://community.fibery.io/t/april-21-2023-breadcrumbs-on-views-strict-relation-filters/4354):
>
> bread Breadcrumbs on Views Sometimes it’s easy to get lost in Fibery with [Context Views](https://the.fibery.io/@public/User_Guide/Guide/Context-Views-20) and, since recently, [Nested Documents](https://the.fibery.io/@public/User_Guide/Guide/Nested-Documents-166). A teammate sends you a link — and you have no idea where you arrived. That’s why we have added (clickable!) breadcrumbs on top of all Views. hammer Strict relation filters [relation-filter-show-other-toggle] Some [Relation Filters and Sorts](https://the.fibery.io/@public/User_Guide/Guide/Relation-Filters-and-Sorts-177) are there just for the end-user’s convenience. Others, though, make sure the right processes are fo…

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [June 16, 2023, 2:12pm UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647/22 "2023-06-16T14:12:23Z")

</div>

I was looking for something you could do with single and multiple-select fields, so with relations not really what I was hoping for. Do you think the very first example at the top of this thread could be handled by the filters? Maybe I don’t understand this well, so if that’s possible, please enlighten me, thank you!

---

<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:** [June 16, 2023, 2:38pm UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647/23 "2023-06-16T14:38:54Z")

</div>

For the example in the first post of the topic, you would need the categories (Meat, Vegetable and Fruit) and the examples (Beef, Pork, Spinach, etc.) to be in databases  
(and it assumes that you would be choosing a single example, based on the value of the category)

The case for relation filters being supported for single-selects is in the backlog.

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [June 16, 2023, 2:52pm UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647/24 "2023-06-16T14:52:27Z")

</div>

Ok thanks for getting back to me. Yes so that’s what I thought. It’s a point frequently made by @Oshyan that I subscribe to pretty strongly as I move along in Fibery and months/years pass, and that is to **avoid creating a db unless it’s absolutely necessary**. In fact my team has many potentially db-level groupings that are instead categorized by using single or multi-selects within one DB so we can avoid setting up too many db’s. Proliferating db’s leads to all kinds of issues that could be solved with [polymorphic](https://community.fibery.io/t/polymorphic-relations-when-creating-relation-ability-to-have-many-types-from-which-to-choose-and-not-just-one-type/425), which is one feature I really hope gets out of the backlog at some point!

So in this case I would definitely not want to create a db just for those few ways of categorizing the entities.

Thanks again!

---

<div class="post-metadata">

**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Post date:** [July 10, 2023, 2:33am UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647/25 "2023-07-10T02:33:25Z")

</div>

This is something I have been coming across repeatedly as well. I fully agree with this sentiment:

> [@B\_Sp](#):
>
> **avoid creating a db unless it’s absolutely necessary**

I think given that single/multi select fields appear to be databases under the hood, it does seem logical that the filter could be extended to them as well. This way the users can extend the database without having to manage it as a full-blown database.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7cd45d5093dd43be1c7c9fed0e588087502f5dc1.png)

This might be mostly psychological but I can imagine it becoming very difficult to manage multiple “Status” databases when all you are trying to do is to allow the “Status” drop-down field to be dependent on another field.

---

<div class="post-metadata">

**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Post date:** [December 15, 2023, 10:12pm UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647/26 "2023-12-15T22:12:55Z")

</div>

Is there any possibility that we will see the filter functionality (as described above) will become a feature in the near future? This would really help keeping the clutter to a minimum.

I know using a separate database has been suggested as a solution. However, I do find that new users are totally confused by the ability to click through the field and get to a “status” entity page. I think having single/multi-select fields be just drop-downs makes them very useful. The fact that you have to make an effort to open them as entities means that users are not confused by the seeing the “ **\>** ”.

See also:

> [@Global single and multi-select field options](https://community.fibery.io/t/global-single-and-multi-select-field-options/2779/9):
>
> Per the suggestion, I’ve gotten in the habit of using databases in many cases instead of single/multi select fields. However, there are a few pain points with this, mostly on the UI front: single/multi select fields can be colour coded and have an icon (though the icon issue I think is already resolved) single/multi select fields have a very simple display both in the entity view and on other views, whereas relations confuse users because they show up with database icons and the “\>” button wh…

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [June 13, 2023, 2:46pm UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647/27 "2023-06-13T14:46:45Z")

</div>

Based on [this thread](https://community.fibery.io/t/field-available-in-database-based-on-another-field/4568) I started in Get Help.

I explored using back refs or highlights, but I want to have a more structured and consistent relationship pattern, so migrating my Get Help question into a feature request/idea.

---

<div class="post-metadata">

**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\
**Post date:** [March 4, 2026, 2:04am UTC](https://community.fibery.io/t/dependent-dropdown-field-type/647/28 "2026-03-04T02:04:35Z")

</div>

> [@B\_Sp](#):
>
> **avoid creating a db unless it’s absolutely necessary**. In fact my team has many potentially db-level groupings that are instead categorized by using single or multi-selects within one DB so we can avoid setting up too many db’s.

Hi. I can see why you would do that to avoid clutter, but as @cannibalflea mentioned, even a regular select field literally creates a database.

Your current approach of keeping _potentially db-level groupings_ as _using single or multi-selects_ has many drawbacks, too. One of which is that it is not easy to do a report across different entity types sharing the same grouping, for examples Clients in Market X, and Staff in Market X.

So, when centralised groupings are needed, I recommend using what I have, for decades:

1. A dimensions table that holds the names of your dimensions, i.e. grouping buckets, e.g. Market, Role, Urgency, Necessity, Impact, Function, etc.
2. An options table that has a one-to-many relation to the Dimensions table, with at least a Label column, though usually I have key, order, parent, recursive label (that ancestors’ breadcrumb), description, status, notes, etc.
3. For any given entity type (database) that you are about to create a select field called X and give it options 1, 2 &3, instead create a relation field to Options, and filter the relation to show Options only from Dimension X. You can even sort them according to your needs.

Hope this helps.

[Previous page](https://community.fibery.io/t/dependent-dropdown-field-type/647.md?page=1)
