# Inheritance of Relation

**URL:** <https://community.fibery.io/t/inheritance-of-relation/1175>\
**Category:** Ideas & Features\
**Created:** [November 16, 2020, 5:57am UTC](https://community.fibery.io/t/inheritance-of-relation/1175 "2020-11-16T05:57:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [November 16, 2020, 10:22am UTC](https://community.fibery.io/t/inheritance-of-relation/1175/2 "2020-11-16T10:22:49Z")

</div>

For what it’s worth, the Binders app I have used a fair bit deals with this in the following way:  
You define a calculation for a field (formula type thing) and you choose one of four behaviours:

- Calculated and stored (i.e. default value)
- Calculated on demand (you click a button to ‘run’ the calculation
- Calculated else entered (as long as the calculation yields a valid result, this overrides any user choice)
- Entered else calculated (as long as the user has made a valid choice, this overrides the calculation)

These options are all independent of whether a field is read-only or not.

And for what it’s worth, the current auto-relations option in fibery seems to be a read-only, calculated field, which is why it can’t provide quite what @B_Sp wants. I guess that he needs either the 3rd or 4th type.

---

_[View the full topic](https://community.fibery.io/t/inheritance-of-relation/1175)._