# \[APPROVED\] Relationships filter

**URL:** <https://community.fibery.io/t/approved-relationships-filter/1364>\
**Category:** Ideas & Features\
**Tags:** flexible-domain\
**Created:** [February 12, 2021, 6:36pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364 "2021-02-12T18:36:54Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Travis](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/travis/32/1490_2.png) [@Travis](https://community.fibery.io/u/Travis)\
**Post date:** [February 12, 2021, 6:36pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/1 "2021-02-12T18:36:54Z")

</div>

It would be great to be able to create a Relation column that only shows a filtered subset of the relevant Type.

So for example, a relation column that only shows Tasks that are already marked “done,” or Expenses that are greater than $100. Etc.

---

<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 12, 2021, 7:26pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/2 "2021-02-12T19:26:38Z")

</div>

I think something similar was talked about last month:

> [@\[DONE\] Filtering like automatic linking](https://community.fibery.io/t/filtering-like-automatic-linking/1304):
>
> It would be nice to use something like filter identical to automatic linking. Instead of auto-linking, I must link them manually, but they are limited by the same filter: I’ve had use for this in various places, e.g. sub-products picking. Last one was for UX research. Example use-case I have a Session with a Participant. I also have Tests, and these Tests have Checkpoints. [image] When creating a Session I will pick which Test we will be performing, and the goal is to meet all the …

Is this close to what you’re talking about @Travis ?

---

<div class="post-metadata">

**Author:** ![Travis](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/travis/32/1490_2.png) [@Travis](https://community.fibery.io/u/Travis)\
**Post date:** [February 12, 2021, 7:36pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/3 "2021-02-12T19:36:42Z")

</div>

@Chr1sG I think so, although it’s not super clearly stated in that thread.

The exact feature I’m hoping for was just released by Google Tables. Not that I’m going to abandon Fibery, but this video clearly shows the functionality I’m describing: [https://youtu.be/uQd5ynbzKLk](https://youtu.be/uQd5ynbzKLk)

---

<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 12, 2021, 7:59pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/4 "2021-02-12T19:59:09Z")

</div>

Yeah, I’m pretty sure it’s the same idea 🙂

---

<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:** [February 13, 2021, 3:04am UTC](https://community.fibery.io/t/approved-relationships-filter/1364/5 "2021-02-13T03:04:05Z")

</div>

@Travis and @Chr1sG I think this well describes what you are looking for as well?

> [@Filtering "Collections" Sub-entity views - Request, and is it done?](https://community.fibery.io/t/filtering-collections-sub-entity-views-request-and-is-it-done/825):
>
> Hello, I wanted to bring up the request to have the ability to filter within the “Collections” area on the Entity card. It’s this area: I have been following two requests for this functionality from @rickcogley and @gregbacchus: This is a great feature and to reaffirm some of what Rich and Greg are saying, the example of a group of tasks that need to be referenced could get long over time if you can’t filter out “done” items, for example. And I d…

You can see in that post a few more examples of the exact same request, which are actually marked “done” but I don’t think they are…

This is also a cornerstone of Notion, although the closed equivalent to “Collections” in Notion is probably a “Linked Database” which doesn’t actually work as well, I think, as in Fibery - for example, there is no automatic relation between a Linked Database and the Page in Notion where you add the Linked Database. But you can do all kinds of filtering, sorting etc. in there that you can’t do in Fibery right now.

I also think colleague @Oshyan is looking for similar functionality with [[DONE] Embed Custom Views into Entity View](https://community.fibery.io/t/embed-views-in-rich-text/936)

Cheers!

---

<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, 2021, 8:41am UTC](https://community.fibery.io/t/approved-relationships-filter/1364/6 "2021-02-13T08:41:36Z")

</div>

I think that functionality is slightly different, since it relates to filtering the display of linked items so that only a subset is shown.  
I believe what Travis is looking for (and me too) is the ability to define the subset of entities that you are allowed to link to, based on a filter.

---

<div class="post-metadata">

**Author:** ![Travis](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/travis/32/1490_2.png) [@Travis](https://community.fibery.io/u/Travis)\
**Post date:** [February 13, 2021, 11:22pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/7 "2021-02-13T23:22:23Z")

</div>

@Chr1sG That’s correct!

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [April 8, 2021, 7:48pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/8 "2021-04-08T19:48:32Z")

</div>

An “Automatically Link” relation currently requires the fields from each entity to be **EQUAL**.

If this requirement was relaxed to allow more flexible rules, would that provide everything we need?

E.g. allow automatic linking with rules like, “field-A is a substring of field-B”, or “field-A is not one of the following values”.

---

<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:** [April 8, 2021, 11:11pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/9 "2021-04-08T23:11:54Z")

</div>

The automatic linking option means that the tool links to everything that matches the filter without any input from the user (giving a read-only field).  
I think the original request is for the tool to limit the available options that the user can pick from (but it’s still an editable field).  
So even if the auto-link rules were more flexible, it wouldn’t meet the need that Travis (and I) have.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [April 14, 2021, 2:38pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/10 "2021-04-14T14:38:29Z")

</div>

We have this in plans under “Filter relation field selector in Entity View” feature.

---

<div class="post-metadata">

**Author:** ![DioniGR27](https://avatars.discourse-cdn.com/v4/letter/d/e495f1/32.png) [@DioniGR27](https://community.fibery.io/u/DioniGR27)\
**Post date:** [October 4, 2021, 12:49am UTC](https://community.fibery.io/t/approved-relationships-filter/1364/11 "2021-10-04T00:49:13Z")

</div>

Is this feature planned for the nearly future?

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [October 8, 2021, 7:41am UTC](https://community.fibery.io/t/approved-relationships-filter/1364/12 "2021-10-08T07:41:39Z")

</div>

Unfortunately no plans for the next 3 months.

---

<div class="post-metadata">

**Author:** ![Simon\_JB](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/simon_jb/32/1453_2.png) [@Simon\_JB](https://community.fibery.io/u/Simon_JB)\
**Post date:** [March 16, 2022, 1:04pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/13 "2022-03-16T13:04:53Z")

</div>

Hello, just checking if this feature is still planned or if the “block” feature would somehow replace it ?

If you have user stories linked to a feature for instance, you can open the feature and see the list of all user stories but you cannot :

- filter that list (to exclude finished stories for instance)
- order that list (by status for instance)
- edit an assignment or a status from this story without opening it first

Another way to do that with the future “blocks” feature might be to create a template for all features that embeds a custom view of all stories attached to those features (this view being sortable or filterable). Is it planned this way ?

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [March 29, 2022, 5:55pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/14 "2022-03-29T17:55:54Z")

</div>

Yes, this is exactly what Blocks will deliver eventually. The roadmap is this:

1. Deliver experimental Page with just Text + Table blocks
2. Add blocks to Entity View and default templates
3. Add more blocks.

I hope it will take us ~2 months to do it all.

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [June 7, 2022, 10:28pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/15 "2022-06-07T22:28:06Z")

</div>

Hmm, not on the [Public Roadmap](https://the.fibery.io/@public/Public_Roadmap/Roadmap-Board-5974)?

---

<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:** [June 8, 2022, 5:45am UTC](https://community.fibery.io/t/approved-relationships-filter/1364/16 "2022-06-08T05:45:53Z")

</div>

> **[Roadmap Board](https://the.fibery.io/@public/Public_Roadmap/Roadmap-Board-5974#Roadmap_Item/Create-relation-Views-on-Entity-View-15)**
>
> Create a custom workspace for all roles in your company. Connected databases, customizable views, powerful reports, automations, integrations, and more. You name it, we have it.

Switching the collection field to a ‘relation view’ will probably cover this.

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [January 17, 2024, 8:58pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/17 "2024-01-17T20:58:12Z")

</div>

This feature is done, I believe.

---

<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:** [January 17, 2024, 9:22pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364/18 "2024-01-17T21:22:32Z")

</div>

Yes and no.  
We have relation filters for to-one relations, but not for to-many fields.
