Hi @markovetski
I’m glad to hear that you found solution.
As for “hidden fields”:
When we are talking about “calculation” type fields this may cause some confusion and I see it in your post so let me explain.
A regular field such as e.g. “input” or “number” can be hidden or not based on visibility conditions that you set for it.
A “calculation” field can be hidden this way too and the “When this field is hidden, should its value be null (zero), or should the field be ignored in calculations” applies to that; if “calculations” field is hidden by visibility rules then
– it can either have value of 0
– or it can be ignored – behave like it was never there.
This is correct and intended behavior because in general, by design hiding fields with visibility conditions is not mean to act the same way as just making field “still there but invisible” – but rather to help build dynamic forms which have or do not have certain fields; so hiding field with visibility condition is like dynamically removing the filed from the form.
For calculations field we have added that option so instead of “removing” it you could make it with value of 0 because otherwise it could be breaking some calculations.
But if you want to keep the calculation field value in the calculation and yet keep the field invisible, there’s another option to hide it – with a “hidden” checkbox on in field’s “settings” tab. But that will not be conditional (so field will be used in calculation but permanently invisible).
There’s no in-betweens here but there is a way around it: instead or in addition to conditionally showing calculations that are only “components” of final calculation – create multiple final calculation in different version using relevant components only and then set those final calculations to show/hide as well based on the same criteria.
—-
With that being said, I understand that you found solution already so I’m posting that only to shed some light on how it works.
We also do have plan to add a third option to “When this field is hidden, should its value be null (zero), or should the field be ignored in calculations?” setting – to actually keep the value; which is exactly what you are suggestion.
That’s already on a list of feature planned in future so we can expect it to be added with one of future updates, though I’m not able to tell when and have no ETA currently.
Another similar feature that can be helpful in such cases would be “conditional (if/else) calculations” which is also something we have in plans (though, again, I have no ETA).
So I believe in future setting up such configurations will be way easier and more robust with those ??
Best regards,
Adam
