# 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\
**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:** 3

<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:** [January 27, 2026, 3:54am UTC](https://community.fibery.io/t/allow-collection-views-to-traverse-to-one-relations/9281/3 "2026-01-27T03:54:03Z")

</div>

I just faced this and its quite a problem… changing it to to-many goes against how the schema should be operated.

My usecase: Project → Steps ← Step Template ↔ Documentation.  
I’d like to show the documentation on the project, but this only gets allows if the steps to step template is many to many.

Somewhat similar to this: [Stop treating "to-one" relation fields like a red-headed stepchild!](https://community.fibery.io/t/stop-treating-to-one-relation-fields-like-a-red-headed-stepchild/8739)

---

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