# \[DONE\] Many-to-many relationships should be usable for levels in lists

**URL:** <https://community.fibery.io/t/done-many-to-many-relationships-should-be-usable-for-levels-in-lists/1624>\
**Category:** Ideas & Features\
**Tags:** list-view\
**Created:** [May 13, 2021, 4:29pm UTC](https://community.fibery.io/t/done-many-to-many-relationships-should-be-usable-for-levels-in-lists/1624 "2021-05-13T16:29:07Z")\
**Posts on this page:** 1\
**Showing post:** 19

<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:** [February 16, 2022, 3:42am UTC](https://community.fibery.io/t/done-many-to-many-relationships-should-be-usable-for-levels-in-lists/1624/19 "2022-02-16T03:42:08Z")

</div>

I think the cases I am presenting are actually one-to-many relations but they involve nesting of entities that have multiple parent types.

> [@ihartrafimovich](#):
>
> 1. Every type can be selected only once (it’s your case I guess);

This is not exactly true. In my case, an entity can have parents of different types but those are one-to-many relations.

For example a person works for a company but can also be part of a department within than company. When I create a hierarchy of organization → organizational unit (department) → contact, Fibery gets confused on where to position the contact: under the organization or the department.

[![](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/441a539f9d46d012c2818dcd85f4f3c666d6f8ac.png) ](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/441a539f9d46d012c2818dcd85f4f3c666d6f8ac.png)

I [described a possible solution in this post](https://community.fibery.io/t/representing-nested-relations/1405/15), basically suggesting to work from the deepest level of the hierarchy upwards to find the first “parent” for the entity.

Now when many-to-many relations are involved, I think the above process could simply be ignored so that the same entity appears multiple times in the hierarchy.

> [@ihartrafimovich](#):
>
> 1. Same-type reference can be selected only on the top level.

I think the approach that I am suggesting above will also address the same-type reference issues at deeper levels of the hierarchy as well. Those situations are generally one-to-many relations between the child and parent nodes.

Apologies if this still doesn’t make sense. It is a rather interesting and challenging issue. If it helps, I can try and describe it to you in a short screen capture or a short zoom call.

---

_[View the full topic](https://community.fibery.io/t/done-many-to-many-relationships-should-be-usable-for-levels-in-lists/1624)._