# Dynamic relation filters for "to-many" relation

**URL:** <https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665>\
**Category:** Ideas & Features\
**Tags:** filter\
**Created:** [April 25, 2025, 9:18pm UTC](https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665 "2025-04-25T21:18:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [April 25, 2025, 9:18pm UTC](https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665/1 "2025-04-25T21:18:25Z")

</div>

When making a dynamic relation filters, it can only use to-one relations as references and not to-many (contains any of). This is a limitation.

Use case: show all other contacts in the company when logging a call. A call can be with multiple people. Maybe from different companies. If I select one person from company x, it should then show me all other people in company x. If I then press someone on company y, it should show everyone in company x and everyone in company y.

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [May 22, 2025, 3:50pm UTC](https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665/2 "2025-05-22T15:50:39Z")

</div>

I think this is related as well: [In embedded Views, allow Filtering on Relation fields for "Is this entity"](https://community.fibery.io/t/in-embedded-views-allow-filtering-on-relation-fields-for-is-this-entity/3635)

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [May 22, 2025, 3:59pm UTC](https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665/3 "2025-05-22T15:59:27Z")

</div>

I don’t think so. But maybe the request is unclear then.

Here’s what I mean:  
This works. Contacts is many to many, Company is many to one.

 ![Screenshot 2025-05-22 at 16.55.50](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5af8eef36c31b0a80be574b0d485efd708986cf2.jpeg)

When you change the company to “to-many”:

 ![Screenshot 2025-05-22 at 16.55.58](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7e134e017a242de441706f4658f50f848f47ba09.jpeg)

Dynamic filtering no longer works.

 ![Screenshot 2025-05-22 at 16.56.43](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7a2de1336e343151e302aa30982467fc1edbd482.jpeg)

---

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [May 22, 2025, 4:09pm UTC](https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665/4 "2025-05-22T16:09:48Z")

</div>

You’re not wrong, they are different enough (yours is about the relation/link UI and the other is about the filtering UI) but they’re both related to gaps in dynamic/context filtering so I wanted to make sure they were generally linked. I think context filtering is currently half-baked and needs major expansion/improvement.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [May 22, 2025, 4:52pm UTC](https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665/5 "2025-05-22T16:52:14Z")

</div>

I see, makes sense! Agreed that context it’s such big selling point of Fibery, yet the way it works right now results in a subpar experience in different areas. (Just the fact that is works in such different ways in different places)

---

<div class="post-metadata">

**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Post date:** [June 12, 2025, 6:08pm UTC](https://community.fibery.io/t/dynamic-relation-filters-for-to-many-relation/8665/6 "2025-06-12T18:08:41Z")

</div>

I just ran into this issue. And I realize this is actually pretty critical for building out data hierarchy across 3 or more databases.

With context filtering you can essentially nest databases within each other such that records are only available if the parent database is the same between child databases.

Database A (Parent of B & C - One to Many)  
Database B (Child of A - Many to One) (Many to Many Relationship with C)  
Database C (Child of A - Many to One) (Many to Many Relationship with B)

When linking records of B and C together only the records that are linked to the Parent Database A should be available.

To do this we need a dynamic filter on the Many to Many Field Views so that only those items appear.
