Value inserted on "Form Calculation widget" using "Conditional logic" disappears during submission

  • Profile Image
    Asked on January 15, 2016 at 10:36 AM

    Hi there. I'm just trying to understand something from a mistake that I made in my form.

    Is it generally a bad idea to put conditions on a calculation widget field?

    I see that I did this several times on my form and apparently it's creating some kind of circular logic. I'm trying to figure out the source of my error, and I think I was duplicating a Calculation Widget field thinking that it was a Number field. Then I applied Calculation Conditions on top of it. Probably a bad idea, right?

    Thank you for any further explanation you can give on a situation like this.

  • Profile Image
    Answered on January 15, 2016 at 01:02 PM

    Our developers are working on the new conditions wizard, so there might be some updates, fixes, changes that might caused the error. These observations are very important to help improve the features we have.

    Currently, your observation is indeed correct, the "Form Calculation" widget seems to not permanently fetch the value when the source is the conditions. We know that the widget has it's own calculation settings.


    See this sample form: I have a condition that add "Num 1" and "Num 2" based on condition and not directly on the settings of the widget. Here's how I replicated the problem:

    1. Fill out "Num 1" and "Num 2"

    2. When you submit, the value disappears, it looks like the script is trying to check if the value is directly on the widget's setting on input, ignoring the condition that was previously triggered.


    I am not quite sure if this is caused by an update on the new conditions or on the form calculation widget itself. So far, it seems like this setup does not work, but I cannot say that it is a bad practice.


    I will forward this to our developers to have it checked. They can probably make adjustments or improvements based on this. We will update you as soon as there are changes implemented.

  • Profile Image
    Answered on January 15, 2016 at 01:08 PM

    I think it would be super-fabulous (and it would have saved me countless number of hours of confusion) if there was some kind of a warning when a person tries to put calculation conditions on a calculation widget field. As a beginner I did not even realize that there were 2 different ways to make a calculation, and apparently I tried the one, then tried the other, and did not realize I was doing the same thing with 2 different methods on the same field. It also likely happened in other places because I was duplicating a Calculation Widget field thinking that it was a number field, and not realizing there was a calculation inside that might fight with the Calculation Conditions I was applying on top of it. Thank you so much for your assistance and explanation.

  • Profile Image
    Answered on January 15, 2016 at 02:38 PM

    No worries, I'm glad the information shared above helped you. Personally, I think it is quite tricky or perhaps complex to have a validation to check if there are conflicting conditions or calculations, but it is a good thought. This flexibility of the features and functions allows you to create complex process flows, although sometimes it might conflict with one another depending on how they are setup.

    As a beginner, you have already made good observations with our form builder. There will always be some confusion when using a new tool, but the support team will always be here to help you on any concern, question or problems you encounter. Please do feel free to ask us anything here in the forum. We'll be more than happy to help.

    Thank you.

  • Profile Image
    Answered on January 19, 2016 at 03:24 AM


    This issue has now been resolved.  Readonly calculation fields with empty calculations that are used as conditional result fields for conditional calculations will no longer be cleared on form submission.

    Please let us know if you continue to have problems.