# View levels: Show relationship field if there are multiple relations to the same DB

**URL:** <https://community.fibery.io/t/view-levels-show-relationship-field-if-there-are-multiple-relations-to-the-same-db/5838>\
**Category:** Ideas & Features\
**Created:** [February 11, 2024, 2:58pm UTC](https://community.fibery.io/t/view-levels-show-relationship-field-if-there-are-multiple-relations-to-the-same-db/5838 "2024-02-11T14:58:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [February 11, 2024, 2:58pm UTC](https://community.fibery.io/t/view-levels-show-relationship-field-if-there-are-multiple-relations-to-the-same-db/5838/1 "2024-02-11T14:58:57Z")

</div>

Allow Views Levels to select the relationship instance if there are multiple relations to the same DB  
This is a pretty common scenario I run into.

~~This can be considered an ‘issue/bug’ because the Levels selection feature is not working in certain scenario where we want to show a specific relation, and applies random selection.~~

 ![chrome_WtV0emUEYp](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5e06e88425d35964d821f9f5a4a58bd3dadbffff.jpeg)  
.

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [February 11, 2024, 5:23pm UTC](https://community.fibery.io/t/view-levels-show-relationship-field-if-there-are-multiple-relations-to-the-same-db/5838/2 "2024-02-11T17:23:43Z")

</div>

I just discovered that you CAN select the database that is crossed through, and the view will use the ‘other’ relationship field of the same database. That is good!

However, it is counter-intuitive to click on a crossed-through database, so better would be if the relationship **field name is appended to the database name** in the select box. So changed this topic from ‘bug/issue’ to ‘feture request’. 🙂
