Trying to understand why code toString(abs(round(netamount,2))), "|", is generating additional zeros

[RAHUL_singh1]

Trying to understand why code toString(abs(round(netamount,2))), “|”, is generating

[duncan]

Hello @RAHUL_singh1

That’s pretty interesting, I’ve never run into this myself but I’ve seen issues with decimal places come up before.

The first thing I would try is checking the data type of netamount. If its currently decimal float you could try changing it to decimal fixed.

Also, a user a while ago found a workaround for a similar issue. You could try adding the logic from the calculation in the solution from this topic into your calc above:

Calculations introducing extra decimal places

I noticed that sometimes my calculations add extra decimal places to my numbers. For example, the numbers in the screenshot below are calculated but they should be exactly 45, 25, 45, 50, 45, 60 and 45 respectively. When I export this visual to CSV, I don’t see all the extra decimal places. Normally this would be fine because I can easily set the number of decimal places to 0 at the visual level. The problem is when I add a top/bottom filter, QS doesn’t correctly identify ties because of all th…

[RAHUL_singh1]

Hi @duncan , Thanks for your response . I tried with decimal(float) and decimal(fixed) both. Also in my Athena dataset I tried to cast(netamount as decimal(18,2)) but still same output.

[duncan]

Hey @RAHUL_singh1

If updating the data type didn’t work then I would try the calculation from the solution in the linked topic from my comment above.

[duncan]

Hey @RAHUL_singh1

Were you able to try the calculation in the topic I linked above?