# 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:** 1\
**Showing post:** 24

<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!

---

_[View the full topic](https://community.fibery.io/t/dependent-dropdown-field-type/647)._