# New relation to the same entity type could be more intuitive

**URL:** https://community.fibery.io/t/new-relation-to-the-same-entity-type-could-be-more-intuitive/3183
**Category:** Ideas & Features
**Created:** [August 18, 2022, 10:48am UTC](https://community.fibery.io/t/new-relation-to-the-same-entity-type-could-be-more-intuitive/3183 "2022-08-18T10:48:09Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![HereBeBeasties](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/herebebeasties/32/5429_2.png) [@HereBeBeasties](https://community.fibery.io/u/HereBeBeasties)
#### Post date: [August 18, 2022, 10:48am UTC](https://community.fibery.io/t/new-relation-to-the-same-entity-type-could-be-more-intuitive/3183/1 "2022-08-18T10:48:10Z")

</div>

When adding a field to an Entity that refers to itself:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a35883ec9258da0170d007a37d7b5161abd920a7.png)  
…but IMO it’s rather unobvious how the relationships work and what the fields I will end up with are.

Good things:

- The suggested field name is “Users” which helps me realise I’m going to get a one:many relationship
- The “Direction” panel has the “one” relationship first followed by the “many” relationship

Bad things:

- As soon as I type “Manager” into the field name, I feel rather lost - which end of the relationship is which? In the UI it’s all just “User”
- It says “Add field” on the button but I actually get _two_ fields, one at each end
- I don’t get to name the other field that gets created at the other end of the relationship - it just gets created as “Users”; I should be able to name it as “Reports” in the same step

Perhaps the UI could look like this instead:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/5/5c5f6cb1c1f1abd96ddb5dd6144ecde9208fbc85.png)

Note that most of the above is probably valid for adding any relationship, and not just one that references the same entity type. Adding a relationship to the same type is most confusing, though.

---

<div class="post-metadata">

### Author: ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)
#### Post date: [August 18, 2022, 2:17pm UTC](https://community.fibery.io/t/new-relation-to-the-same-entity-type-could-be-more-intuitive/3183/3 "2022-08-18T14:17:31Z")

</div>

This is a very good point and an interesting solution.

---

<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: [August 18, 2022, 3:19pm UTC](https://community.fibery.io/t/new-relation-to-the-same-entity-type-could-be-more-intuitive/3183/4 "2022-08-18T15:19:43Z")

</div>

Maybe it could be even simpler…

For self-relations:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0f8cc29d8c9cdbc9c6127e61cf94be85c8bb6396.png)

For inter-db relations:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/c/cc3d4b556ae7a2174f9218a18d65e6e5a1ecfa81.png)

---

<div class="post-metadata">

### Author: ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)
#### Post date: [August 18, 2022, 4:37pm UTC](https://community.fibery.io/t/new-relation-to-the-same-entity-type-could-be-more-intuitive/3183/5 "2022-08-18T16:37:03Z")

</div>

Yes, this has bugged me for a long time! Love the mockups, that definitely shows a more intuitive approach IMO.