# Allow Collection Views to Traverse To-One Relations

**URL:** <https://community.fibery.io/t/allow-collection-views-to-traverse-to-one-relations/9281>\
**Category:** Ideas & Features\
**Tags:** table-view, list-view, context-empire\
**Created:** [July 27, 2025, 12:42pm UTC](https://community.fibery.io/t/allow-collection-views-to-traverse-to-one-relations/9281 "2025-07-27T12:42:10Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [October 9, 2026, 8:23pm UTC](https://community.fibery.io/t/allow-collection-views-to-traverse-to-one-relations/9281/5 "2026-10-09T20:23:32Z")

</div>

> [@RonMakesSystems](#):
>
> I can not make a table on the Org to show the related people…

Well, you can make a lookup, so it seems like this need could be solved if lookup fields looked/behaved like direct to-many relations, right?

> [@Entity context lookup: related field lookup list of relations, not allowing filters and search](https://community.fibery.io/t/entity-context-lookup-related-field-lookup-list-of-relations-not-allowing-filters-and-search/9227):
>
> 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

---

_[View the full topic](https://community.fibery.io/t/allow-collection-views-to-traverse-to-one-relations/9281)._