How to fix some of my calculation field isn't showing any calculated value

  • Profile Image
    Asked on September 07, 2017 at 01:40 PM

    Hi again JotForm Staff,

    As our testing has expanded, we've encountered another glitch in my form "PFI Annual Conference Sponsorship Options" (

    On my A, B, C and D-Level sponsor pages, I have created a SUBTOTAL field (visible in blue color) to show users what their current subtotal is, which includes any add-on fees.

    On the surface, all these Form Calculation widget SUBTOTAL fields appear to work correctly.

    HOWEVER, on the B- and C-Level pages, if you start by clicking "YES, I want to display," enter a couple of options, then change your mind and click "No -- my organization will not exhibit," suddenly, the blue SUBTOTAL fields are empty and do not display anything.

    This does not happen on the A- and D-Level pages. I have checked the set-up of each Form Calculation field, and they are all set up the same (the only variation being the add-ons included in the calculation).

    Any ideas on what's going on? The FINAL TOTAL at the end of the form still correctly displays, but the Subtotal field on the B- and C-Level pages switches to blank if you switch between Yes / No to displaying -- and does not revert back either, even if you select "Yes" again.

    Any ideas what's going on?

    Thanks so much for your help!


  • Profile Image
    Answered on September 07, 2017 at 02:12 PM

    The problem is because you miss to add a number in your calculation value which made the subtotal void (syntax error) since in the calculation widget it is set as "number" .


    In B missing option value is in "Extra Table or Space Needed?" field. Set it to "0" .

    In C, refer to image attached below. Set it to "0" again.

    I hope this fixed the issue. Please reply back if you have more questions.


  • Profile Image
    Answered on September 19, 2017 at 02:39 PM

    Sorry for my slow reply back ... Thanks very much for catching that! I thought I'd checked all those, but apparently missed some. 

    I'm just getting back to making the final tweaks on this form, so hopefully this fix solves this particular issue. I'll let you know if it doesn't.

    Thanks again for your help and swift reply!