KB-1426 Unexpected results on decimal calculations and rounding

Parmida Borhani — Tue, 12 Dec 2017 18:53:21 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 12/12/2017 6:53:21 PM

Symptom

Designers will sometimes receive unexpected rounding/results for calculations involving decimals. See some examples below:

Observed: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = -1.455192e-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Observed: a!textField(value:12.236319) = 12.23632
Expected: a!textField(value:12.236319) = 12.236319

Cause

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. There is no such thing as perfect precision with double floating point numbers since base 10 numbers are being represented as base 2 numbers.

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding with the round() function, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

If a decimal calculation using the fixed() function is providing unexpected results, try using round() in conjunction with fixed(). For the above example,

fixed(round(8192.80*100),0,true()) = 819280

If the text() function seems to incorrectly round a number, try using less digits after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

If the Text Component is rounding a decimal rule input, try wrapping the fixed() function to indicate the desired number of digits after the decimal to be maintained. For the above example,

a!textField(value: fixed(12.236319,6) = 12.236319

There is a Decimal (Floating Point) Component that can be used.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2017

Tags: known issues, SAIL, application design

KB-1426 Unexpected results on decimal calculations and rounding

Parmida Borhani — Tue, 12 Dec 2017 18:49:21 GMT

Revision 21 posted to Appian Knowledge Base by Parmida Borhani on 12/12/2017 6:49:21 PM

Symptom

Designers will sometimes receive unexpected rounding/results for calculations involving decimals. See some examples below:

Observed: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = -1.455192e-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Observed: a!textField(value:12.236319) = 12.23632
Expected: a!textField(value:12.236319) = 12.236319

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding with the round() function, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

If a decimal calculation using the fixed() function is providing unexpected results, try using round() in conjunction with fixed(). For the above example,

fixed(round(8192.80*100),0,true()) = 819280

If the text() function seems to incorrectly round a number, try using less digits after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

If the Text Component is rounding a decimal rule input, try wrapping the fixed() function to indicate the desired number of digits after the decimal to be maintained. For the above example,

a!textField(value: fixed(12.236319,6) = 12.236319

There is a Decimal (Floating Point) Component that can be used.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations and rounding

Parmida Borhani — Tue, 12 Dec 2017 18:48:15 GMT

Revision 20 posted to Appian Knowledge Base by Parmida Borhani on 12/12/2017 6:48:15 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Observed: a!textField(value: 12.236319) = 12.23632
Expected: a!textField(value: 12.236319) = 12.236319

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding with the round() function, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

If a decimal calculation using the fixed() function is providing unexpected results, try using round() in conjunction with fixed(). For the above example,

fixed(round(8192.80*100),0,true()) = 819280

If the text() function seems to incorrectly round a number, try using less digits after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

If the Text Component is rounding a decimal rule input, try wrapping the fixed() function to indicate the desired number of digits after the decimal to be maintained. For the above example,

a!textField(value: fixed(12.236319,6) = 12.236319

There is a Decimal (Floating Point) Component that can be used.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations and rounding

Parmida Borhani — Tue, 12 Dec 2017 18:34:45 GMT

Revision 19 posted to Appian Knowledge Base by Parmida Borhani on 12/12/2017 6:34:45 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding with the round() function, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

If a decimal calculation using the fixed() function is providing unexpected results, try using round() in conjunction with fixed(). For the above example,

fixed(round(8192.80*100),0,true()) = 819280

If the text() function seems to incorrectly round a number, try using less digits after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

There is a Decimal (Floating Point) Component that can be used as well.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations and rounding

Parmida Borhani — Sun, 10 Dec 2017 23:03:02 GMT

Revision 18 posted to Appian Knowledge Base by Parmida Borhani on 12/10/2017 11:03:02 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding with the round() function, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

If a decimal calculation using the fixed() function is providing unexpected results, try using round() in conjunction with fixed(). For the above example,

fixed(round(8192.80*100),0,true()) = 819280

If the text() function seems to incorrectly round a number, try using less digits of precision after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

There is a Decimal (Floating Point) Component that can be used as well.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations and rounding

Parmida Borhani — Sun, 10 Dec 2017 22:44:49 GMT

Revision 17 posted to Appian Knowledge Base by Parmida Borhani on 12/10/2017 10:44:49 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding with the round() function, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

If a decimal calculation using the fixed() function is providing unexpected results, try using round() in conjunction with fixed(). For the above example,

fixed(round(8192.80*100),0,true()) = 819280

If the text() function seems to incorrectly round a number, try using less digits after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

There is a Decimal (Floating Point) Component that can be used as well.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations

Parmida Borhani — Sun, 10 Dec 2017 22:29:30 GMT

Revision 16 posted to Appian Knowledge Base by Parmida Borhani on 12/10/2017 10:29:30 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding with the round() function, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

If a decimal calculation using the fixed() function is providing unexpected results, try using round() in conjunction with fixed(). For the above example,

fixed(round(8192.80*100),0,true()) = 819280

If the text() function seems to incorrectly round a number, try using less digits after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

There is a Decimal (Floating Point) Component that can be used as well.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations

Parmida Borhani — Sun, 10 Dec 2017 22:27:36 GMT

Revision 15 posted to Appian Knowledge Base by Parmida Borhani on 12/10/2017 10:27:36 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

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()) = 819280

If the text() function seems to incorrectly round a number, try using less numbers after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

There is a Decimal (Floating Point) Component that can be used as well.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations

Parmida Borhani — Sun, 10 Dec 2017 22:24:13 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 12/10/2017 10:24:13 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Observed: text(1.9999999999999, "0.00") = 2.00
Expected: text(1.9999999999999, "0.00") = 1.99

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

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()) = 819280

If the text() function seems to incorrectly round a number, try using less numbers after the decimal point. For the above example,

text(1.9999, "0.00") = 1.99

There is a Decimal (Floating Point) Component that can be used as well.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations

Parmida Borhani — Wed, 29 Nov 2017 23:08:54 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 11/29/2017 11:08:54 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

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()) = 819280

There is a Decimal (Floating Point) Component that can be used as well.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: known issues

KB-1426 Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 21:13:00 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 9:13:00 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

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()) = 819280

Support for a true decimal type is on the backlog. There is also a Decimal (Floating Point) Component that can be used currently.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: known issues

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 21:04:18 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 9:04:18 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding, try rounding with more digits of precision or try using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

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()) = 819280

Support for a true decimal type is on the backlog. There is also a Decimal (Floating Point) Component that can be used currently.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: known issues

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 20:30:57 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 8:30:57 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Cause

Workaround

Depending on the calculation, there could be various workarounds to attempt.

If you are seeing unexpected rounding, try rounding with more digits of precision or using the roundup() or rounddown() functions. For the above example,

round(123/240*100,6) = 15.25
roundup(123/240*100,1) = 15.3

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()) = 819280

Support for a true decimal type is on currently on the backlog. There is also a Decimal (Floating Point) Component that can be used currently.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: known issues

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 20:28:03 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 8:28:03 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Cause

Workaround

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) = 15.25

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()) = 819280

This issue is on currently on the backlog.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: known issues

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 20:19:52 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 8:19:52 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Cause

Workaround

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) = 15.25

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()) = 819280

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

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()

Tags: known issues

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 20:15:20 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 8:15:20 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Cause

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.

Workaround

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

Tags: known issues

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 20:14:10 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 8:14:10 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Observed: fixed(8192.80*100,0,true()) = 819279
Expected: fixed(8192.80*100,0,true()) = 819280

Cause

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.

Workaround

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

Tags: known issues

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 20:02:34 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 8:02:34 PM

Symptom

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-011
Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2
Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Cause

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. Some numbers have an infinite number of digits and can not be represented with 100% precision with only 64-bits. This is because a base 10 number is being represented as base 2.

Workaround

fixed() and round()

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

Tags: known issues

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 20:01:53 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 8:01:53 PM

Symptom

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-011

Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(123/240*100,1) = 15.2

Expected: round(123/240*100,1) = 15.3 since the result is actually 15.25

Cause

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. Some numbers have an infinite number of digits and can not be represented with 100% precision with only 64-bits. This is because a base 10 number is being represented as base 2.

Workaround

fixed() and round()

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

Tags: known issues

KB-XXXX Floating Point Arithmetic

Parmida Borhani — Tue, 28 Nov 2017 03:03:56 GMT

Revision 1 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 3:03:56 AM

Symptom

Cause

Workaround

KB-XXXX Unexpected results on decimal calculations

Parmida Borhani — Tue, 28 Nov 2017 01:02:00 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 11/28/2017 1:02:00 AM

Symptom

Receiving unexpected results for a calculation involving decimals. See some examples below:

Observed: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = -1.455192e-011

Expected: 92000 - (7000.27 + 73000.27 + 2000.33 + 9999.13) = 0

Observed: round(somefunction) = 15.01000000000000000000000001

Expected: round(somefunction) = 15.01

Cause

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. Some numbers have an infinite number of digits and can not be represented with 100% precision with only 64-bits. This is because a base 10 number is being represented as base 2.

Workaround

fixed() and round()

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

Tags: known issues