Answered
Permanently deleted user
Why am I unable to use a decimal point in these fields? All of my calculations require it. Also, is there a way to pull a calculation total into another field without doing the calculation again? I want field x to be exactly when field y is, even if on a different screen.
0
Comments
Please sign in to leave a comment.
Thanks for reaching out. For number fields, make sure you have set the decimal places to the number of places you would like it to calculate to. If it is left at the default 0 decimal places, it will assume all values must be an integer. See screenshot below:
As for calculations, yes, a calculation can use values from across screens. Also, rather than having to create the same calculation twice, if all you are looking to do is "summarize" a calculation from a previous screen, you can use our "summary" field type in the app builder.
More on calculations and summaries here. If you have any further questions for our team, we're happy to help!
I have the same issue, and the fixes described in this article do not fix the issue for me. No matter how I configure my app or my number field entry, I get the same "number must be an integer" validation error.
Hi Chris,
Thanks for posting, (and for calling!) - I figured I'd still reply here for the benefit of others who may view this post:
In this case we determined that the validation error was actually being caused by hidden fields in your app that were pulling reference data with a conflicting number of decimal places - once the decimal places for hidden fields are fixed to match what is contained in the reference data, this behavior should be resolved.
I also recommend keeping all fields visible while testing app functionality. Once it's determined that the set up works, you can go through the app and hide any fields that don't need to be seen while filling out the form.
Have a great day!
I have the same problem with decimals, the calculation does not accept constants smaller than 1. if you put a constant 0.4 it always calculates with 4. how can we fix this?
Hi Tobias Hyrenbach
Thanks for posting to the Community! First, which Builder are you using? The Legacy Builder, which looks more similar to the screenshots above, or the new Builder? Second, have you adjusted the decimal settings for the calculation field? I know sometimes the decimals are finicky but this may not be you, this may be something we want our Support team to investigate.
Please take a look at this article about Setting Up a Calculation Field in the Builder or Setting Up a Calculation Field in the Legacy Builder.
If that still doesn't work, I'll make a ticket for your post so our team can try to reproduce the issue.