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.
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!
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!
Please sign in to leave a comment.
Comments
3 comments