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.