[✅ Solution] Changes in calculation fields?

🙏 Ask the Community
1

Hi,
Are there any changes recently made to the calculation fields? I noticed yesterday I couldn’t create a calculation field as we used to because it asks for a mandatory reference for another field. What is this?

Thanks.
R.J.

1 Like
2

Hi @R.J,

thanks for sharing your question and for reaching out.

Indeed, we “tested” allowing calculation fields without field references for a while, but unfortunately noticed a couple of annoying issues with that behaviour during the test phase. We thereby decided to reintroduce the requirement for at least one mandatory field reference for now to prevent user frustration and confusion.

We are optimistic that we may resolve this properly in the future, as it reduces load and prevents workarounds.

Will keep you posted on that! Also feel free to create a dedicated feature request for that here in the community, so we can track user engagement.

Thanks for your support and understanding!

Cheers
Tim

Update: Creating a hidden field that can be referenced is indeed a viable solution and also shows empathy for our infrastructure - it is quite efficient. As that field will never be changed, useless recalculations are avoided. Thanks for proposing that in your other post.

3

Hi @Tim,
Thanks a lot for the reply. Alright, if you will remove it in the future I will then wait for the changes. So I understand that there is no need to create a specific feature request (if it is already planned and going to be done anyways). But please, correct me if I’m wrong.

Sorry because I think I asked in the other post, is this reference field having any implication at all that we may be careful with when setting it?

Thanks a lot @Tim
R.J.

1 Like
4

Yes, sounds like a plan @R.J. :slight_smile:

The reference field should not have any implication at all, so no need to be “specially careful” here in any way.

Cheers
Tim

1 Like
5

Many thanks for your hints Tim.

1 Like