# References reloaded

**URL:** <https://community.fibery.io/t/references-reloaded/4879>\
**Category:** Ideas & Features\
**Created:** [August 1, 2023, 4:40am UTC](https://community.fibery.io/t/references-reloaded/4879 "2023-08-01T04:40:55Z")\
**Posts on this page:** 1\
**Showing post:** 70

<div class="post-metadata">

**Author:** ![Egor\_K](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/egor_k/32/9710_2.png) [@Egor\_K](https://community.fibery.io/u/Egor_K)\
**Post date:** [July 30, 2024, 4:35pm UTC](https://community.fibery.io/t/references-reloaded/4879/70 "2024-07-30T16:35:00Z")

</div>

The link in this message seems to be dead. So, I’ll ask here: are there any plans to add fields for Relations?  
Adding even the weights and directions of Relations makes their analysis more in-depth, so I totally agree with @Yuri_BC

> [@Relationship properties](https://community.fibery.io/t/relationship-properties/887/14):
>
> As a social systems developer, I am a huge fan of relationship properties, since they reveal the meaning in relationships, and much more information is available to work with in analytics.
> 
> I have tried to workaround this in Fibery using an entity type with endpoints A and B and automation buttons, but it is cumbersome and does not really work well in practice.
> 
> I think that the idea of relationship properties is very well aligned with the character and value of Fibery and will bring Fibery to the next level of interconnectivity and analysis of data.

I love Fibery so much, but the lack of this feature nullifies almost all of its advantages for me 😔

---

_[View the full topic](https://community.fibery.io/t/references-reloaded/4879)._