# Entity context lookup: related field lookup list of relations, not allowing filters and search

**URL:** <https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227>\
**Category:** Get Help\
**Created:** [July 18, 2025, 2:03am UTC](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227 "2025-07-18T02:03:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [July 18, 2025, 2:03am UTC](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227/1 "2025-07-18T02:03:47Z")

</div>

I have a one-to-many relationship with a lookup against a one-to-many. Relationship below.

[A] 1 — \* [B] 1 — \* [C]

In this situation, I want to list all of C in the context of A.

So on the A database, I created a lookup against B’s list of C entities.

This works fine for pulling the data through, but it doesn’t allow:

- displaying in a table (just a list)
- filtering or searching the resultant list

---

<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:** [July 18, 2025, 5:40am UTC](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227/2 "2025-07-18T05:40:24Z")

</div>

Add a relationship from a to C. This relationship will always stay empty, in the description of the field leave a note tgats to make a view and to keep it empty. You can also add a relation filter for where public ID is -1, this the drop-down will always be empty.

Then in the entity view, go to this new relation, and press on “Filter” and the it will say “Show C from a” press on C, and it will give you the option to show c from B from a. Now it will act like a lookup but with the ability to create, and show as any layout. Down side is that it makes a fake relationship, but until this: [Add Views to Entities](https://community.fibery.io/t/add-views-to-entities/8986) makes systems or this: [Add a view of "Collection" entities within another entity that are not related, just for reference](https://community.fibery.io/t/add-a-view-of-collection-entities-within-another-entity-that-are-not-related-just-for-reference/568)  
I think this is the only option.

Note that in table view this fake relationship should be off, and the lookup should be on. As this complex filtering only works in entity view and not in a compact list unfortunately.

Lmk if it works!

---

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [July 18, 2025, 6:01am UTC](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227/3 "2025-07-18T06:01:52Z")

</div>

I could do this…

Daga kotowaru

I’ll just tell users that it’s not possible at this time.

---

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [July 18, 2025, 6:02am UTC](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227/4 "2025-07-18T06:02:48Z")

</div>

Also, if entities get true views… then we could be seeing entity context dashboards in the future 👀

---

<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:** [July 18, 2025, 6:11am UTC](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227/5 "2025-07-18T06:11:07Z")

</div>

Hahah okay.

Because it adds fake data fields or?

> [@AdVhPkgKad](#):
>
> then we could be seeing entity context dashboards in the future 👀

I hope so!! That’s ideal direction I think for entity view. To treat it like a dashboard. [What if entity view was treated as a dashboard?](https://community.fibery.io/t/what-if-entity-view-was-treated-as-a-dashboard/8322) But they said it’s much more complex to build a dashboard layout for entity view than the normal dashboard view. So Idk how long that will take.

---

<div class="post-metadata">

**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Post date:** [July 18, 2025, 6:22am UTC](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227/6 "2025-07-18T06:22:23Z")

</div>

I see as it potentially just being another tab view which you can expand to full-screen. Use some smart CSS to wrap the columns/grid to half-size when viewed in a split panel. Could work

---

<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:** [July 18, 2025, 7:57am UTC](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227/7 "2025-07-18T07:57:29Z")

</div>

Maybe you want to vote for this:

> [@Add display options and more view types for lookup relations](https://community.fibery.io/t/add-display-options-and-more-view-types-for-lookup-relations/5330):
>
> I just noticed today that lookup fields that return \*-to-many relations are automatically rendered as list views. So unlike other relation fields, you are not able to create a different view type (grid, map, calendar, …). Even the list view seems to be a stripped-down version which does not offer the same customization as normal list views (i.e. no sorting, no colour coding …) . You are able to select the fields to be displayed. However, the order the fields are displayed cannot be changes and …
