# Allow many-to-many pickers (multi-select) to be filtered by related-record field once deployed

**URL:** <https://community.fibery.io/t/allow-many-to-many-pickers-multi-select-to-be-filtered-by-related-record-field-once-deployed/9387>\
**Category:** Ideas & Features\
**Created:** [August 8, 2025, 12:39pm UTC](https://community.fibery.io/t/allow-many-to-many-pickers-multi-select-to-be-filtered-by-related-record-field-once-deployed/9387 "2025-08-08T12:39:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Bayly](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mark_bayly/32/12341_2.png) [@Mark\_Bayly](https://community.fibery.io/u/Mark_Bayly)\
**Post date:** [August 8, 2025, 12:39pm UTC](https://community.fibery.io/t/allow-many-to-many-pickers-multi-select-to-be-filtered-by-related-record-field-once-deployed/9387/1 "2025-08-08T12:39:44Z")

</div>

I’m designing a Digital Asset Manager inside Fibery and want two separate tag fields—Context and Subject—pulling from a single Tags DB that includes a Type field (Context/Subject).  
I discovered that relation filtering currently only works with one-to-one relations; many-to-many pickers (multi-select) cannot be filtered by related-record field once deployed.  
This forces us into workarounds like creating separate tag databases for each tag type, which is unsustainable across a large system.  
Please add support for filtered many-to-many pickers so fields like “Context Tags” and “Subject Tags” can share a Tags DB but still display only relevant options.  
This limitation significantly hampers taxonomy design across complex systems.

---

<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:** [August 8, 2025, 1:03pm UTC](https://community.fibery.io/t/allow-many-to-many-pickers-multi-select-to-be-filtered-by-related-record-field-once-deployed/9387/2 "2025-08-08T13:03:00Z")

</div>

Actually, relation filters are available for any relation field, provided the field is a ‘compact field’.

So if you have a collection field in 1-column layout, and you move it above (to the compact section) the option to set a relation filter will appear.

Bear in mind though, relation filters are not strict constraints on the data. A user could potentially link items that do not meet the filter criteria via other means (e.g. drag and drop on board view, via API, etc.)

---

<div class="post-metadata">

**Author:** ![Mark\_Bayly](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mark_bayly/32/12341_2.png) [@Mark\_Bayly](https://community.fibery.io/u/Mark_Bayly)\
**Post date:** [August 8, 2025, 11:29pm UTC](https://community.fibery.io/t/allow-many-to-many-pickers-multi-select-to-be-filtered-by-related-record-field-once-deployed/9387/3 "2025-08-08T23:29:45Z")

</div>

Thanks Chris. Let me try that and see if I can get it to work. This is all brand new to me.

---

<div class="post-metadata">

**Author:** ![Mark\_Bayly](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mark_bayly/32/12341_2.png) [@Mark\_Bayly](https://community.fibery.io/u/Mark_Bayly)\
**Post date:** [August 9, 2025, 12:24am UTC](https://community.fibery.io/t/allow-many-to-many-pickers-multi-select-to-be-filtered-by-related-record-field-once-deployed/9387/4 "2025-08-09T00:24:11Z")

</div>

Chris - Is there a link to a resource that shows me how to do it? I can drag the field above the line but it doesn’t give me any more options and I can’t find any filter operations. I’ll contact support otherwise to help. Thanks Mark
