Prevent Conditionally-Hidden Calculated Fields from Evaluating

Feature Requests
, , ,
1

https://docs.gravityforms.com/conditional-logic-limitations/ states “When Gravity Forms hides a field via conditional logic, it resets the field’s initial value. Conditional logic dependent on this field will be evaluated with that reset value rather than an empty value which is unexpected.”

I may be mistaken, but it seems to me that the performance of larger forms could be significantly improved if calculated fields hidden by conditional logic were reset to “0” rather than being evaluated at client side using Javascript (https://docs.gravityforms.com/enable-conditional-logic/#performance).

2

Am I mistaken? If not, is this a complicated performance improvement to implement?

3

I would not expect this to be a significant performance enhancement as conditional logic would still need to be re-evaluated on these fields since the value of the field is still changing.

1 Like
4

@david, Thank you for clarifying.