# \[APPROVED\] Polymorphic relations. When creating relation, ability to have many Types from which to choose, and not just one Type

**URL:** <https://community.fibery.io/t/approved-polymorphic-relations-when-creating-relation-ability-to-have-many-types-from-which-to-choose-and-not-just-one-type/425>\
**Category:** Ideas & Features\
**Tags:** flexible-domain\
**Created:** [November 22, 2019, 12:14am UTC](https://community.fibery.io/t/approved-polymorphic-relations-when-creating-relation-ability-to-have-many-types-from-which-to-choose-and-not-just-one-type/425 "2019-11-22T00:14:24Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [July 8, 2020, 4:45am UTC](https://community.fibery.io/t/approved-polymorphic-relations-when-creating-relation-ability-to-have-many-types-from-which-to-choose-and-not-just-one-type/425/7 "2020-07-08T04:45:09Z")

</div>

Sorry for posting in this thread again, but this is a big want of mine from Fibery, and wanted to reach out to a few of the newcomers @Jean as well as @chris.burchartz and @Raphael_Mizrahi, who we talked together around this request:

> [@Conditional fields in apps](https://community.fibery.io/t/conditional-fields-in-apps/757/3):
>
> Thanks for the reply. In my humble opinion, this should rank high in your priorities because I do believe this to be a very important feature in many sectors. For instance in real estate, there is a lot of data to collect for listings. A lot of it is conditional, i.e if it’s a house, we’re gonna need to fill field A and B, if it’s an apartment we need to fill C and D, and so on. If your business has any kind of complexity with many data points, you end up with potentially dozens of fields. Hav…

I have done a lot of work in Notion and Coda, and they both have the major limitation of being able to relate just one table to another. Here in Fibery, Types are grouped in Apps, but we still can only relate one type to another. So I find myself making some “mini” hierarchies within Apps, let’s say I have one for Development like “epic - \> feature - \> User story”. If I want to create another Type for an “Engineering Meeting,” I’d like to be able to reference anything out of this App in one field, and potentially see multiple types in that field, too.

I wanted to bring this to your guys’ attention and get your thoughts, as Michael is weighing in here that the team has this on the radar. I personally can’t wait for it! I am curious mainly of any sentiment about how badly it is needed among others using Fibery, or are there any workarounds? I haven’t found any, and simply am waiting impatiently so I can get my Entities into a much more compact state with far fewer fields.

Thanks!

---

_[View the full topic](https://community.fibery.io/t/approved-polymorphic-relations-when-creating-relation-ability-to-have-many-types-from-which-to-choose-and-not-just-one-type/425)._