Decimal precision - Alteryx finds additional precision where hidden/does not exist?

I have an .xlsx file with values where there are two digits after the decimal. I have checked in excel, and I cannot see anything beyond that.

For example, the value: 917285.43 in becomes 917285.43000000000000000000000000000000000000000000000000 when I take it x number of places past the decimal point in Excel.

However, when I bring into Alteryx and take it to 40 digits past the decimal point, Alteryx gives:

917285.4300000000512227416038513183593750000000

Does anyone know why? I think the Excel was outputted from a database. Is it that Alteryx can read these additional digits but excel cannot?

Tips and Tricks

Common Use Cases

Best Practices

Accepted answers

StephenRuhl

Looks like our last posts were lost to the ether.

It looks like Excel just takes your last explicit digit and pads it with zeros to hide the floating point issue. Unless you are using the FixedDecimal data type you will see this issue. It is a known characteristic of computer processing and number storage. Alteryx mentions it in their Help FAQ: I am using a simple filter:[Value] > 2. Yet I am getting values equal to 2 in my TRUE stream. Is this a bug?