You are currently reviewing an older revision of this page.
Designers will sometimes receive unexpected results for calculations involving decimals. See some examples below:
Observed: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = -1.455192e-011Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0
Observed: round(123/240*100,1) = 15.2Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25Observed: fixed(8192.80*100,0,true()) = 819279Expected: fixed(8192.80*100,0,true()) = 819280
This is not a bug with Appian, but it is rather a limitation of the IEEE 754 standard. The Appian Data Type 'Number (Decimal)' is stored as double precision floating-point decimal, which is a 64-bit IEEE 754 floating point. This means that numbers with an infinite number of digits cannot be represented with 100% precision with only 64-bits since base 10 numbers are being represented as base 2.
Depending on the calculation, there could be various workarounds to attempt.
If you are seeing unexpected rounding, try rounding with more digits of precision. For the above example,
round(123/240*100,6)
If the fixed() function is used with a decimal calculation and the results are unexpected, try using round() in conjunction with fixed(). For the above example,
fixed(round(8192.80*100),0,true())
https://home.appian.com/suite/tempo/news/entry/b-263387
https://home.appian.com/suite/tempo/news/entry/f-236747
https://forum.appian.com/suite/tempo/news/entry/f-233757
For forms, use one of the following Text Functions to display a decimal number as a default value to avoid rounding.fixed()text()Also for forms, use one of the following currency functions to display a decimal number as a default currency value.dollar()euro()pound()yen()currency()