- BenitaGAsherAsked on May 24, 2017 at 02:39 PM
My form is here: https://form.jotform.us/71435563653156
I have three number fields near the bottom for user-enterable donation amounts. I have a hidden calculation field that adds these together and displays the total in the PayPal payment field. However that total shows no decimals, so $10+$10+$10 gives 3000 in the total field. I'd prefer not to use decimals at all (ie, have it show 30 in the total) but 30.00 would be OK too.Also, the total doesn't seem to calculate if I only enter a value in the first number field (General Fund donation amount). If I enter a number then tab out of the field, no calculation. But then if I enter a number in the second donation field (transportation), it calculates. I need it to calculate whether the user enters any one or all of the fields. It is most likely scenario that they will only enter one type of donation.
Thanks for your help.Page URL:
- JotForm SupportKevin_GAnswered on May 24, 2017 at 04:26 PM
I have tested what you mentioned about the calculated value not properly passed to the payment field and I can replicate the issue.
Seems like it happens when the value has decimals, example:
Seems like the payment field is not correctly interpreting the passed value, I will report this to our second level since the payment field should be capturing the value with decimals as well.
In the meantime, you could set your calculation widget to do not use decimals:
Regarding to your second question, I have moved it to a different thread, we will assist you as soon as possible here: https://www.jotform.com/answers/1153890
- BenitaGAsherAnswered on May 24, 2017 at 04:51 PM
Thanks, setting the decimal places to 0 is an acceptable workaround for me. I just didn't know how to do it!
- JotForm SupportMikeAnswered on May 25, 2017 at 04:11 PM
Our developers have applied a fix. The decimal point should not be replaced with the comma anymore.
- JotForm SupportwidgetsAnswered on May 26, 2017 at 05:43 AM
Hi we apologize for the late response. It was already fixed since yesterday. Please give it a try and let us know if the problem persist.