# Dependent Dropdown Field Type **URL:** \ **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:** 1\ **Showing post:** 26
**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")
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… --- _[View the full topic](https://community.fibery.io/t/dependent-dropdown-field-type/647)._