# \[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:** 52

<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:** [February 13, 2022, 6:03pm 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/52 "2022-02-13T18:03:18Z")

</div>

Sounds a bit like what’s discussed here

> [@How to best model Hierarchical Types?](https://community.fibery.io/t/how-to-best-model-hierarchical-types/1907):
>
> I want a “parent Type” of Project, with “sub-types” for Website Project and Brochure Project. The parent Project Type will have things like Tasks relation, Assignments, Due date, etc. The sub-types will have details unique to their project type. What is the best way to model this cleanly? Everything I try has undesirable limitations. disappointed_relieved related:

---

_[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)._