Still ROUND issues with EXACT?

Hi,

I was under the assumption that the EXACT rounding method had fixed the issues with floating decimals?

My use case requires several rounded export modules out of one calculation module and thought it's good practise to use ROUND() only once in the calculation module and not in every export module.

Yet, I just discovered that it's still causing issues when the rounded result is used in further (even very simple) calculations. Please see below a replication of it.

First screenshot shows the round formula, second a basic calculation after round.

I will send this for investigation to Anaplan Support, but wondered if there's any additional recommendations on how to use ROUND() with EXACT?

Anapedia doesn't state any limitations.

Screenshot 2020-11-16 at 10.03.47.png

Screenshot 2020-11-16 at 10.04.39.png

Accepted answers

PhilippErkinger

@Misbah I finally received feedback from Level 3 support. They gave me the following explanation:

Ultimately, as the calculation is 2.2 * 2.2, this will produce 4.840000000000001 as the resulting line item value.
The recommendation is to apply the ROUND function with EXACT parameter on the resulting line item value (on the output module and not the system or calculation modules). In the example provided in your screenshots, the ROUND function with EXACT parameter should be applied on the “Use of rounded number” line item as its the resulting line item.
The floating decimal precision value is not an Anaplan issue but the way a computer (international IEEE 754 standard) handles calculation. The ROUND function with EXACT parameter was created to address this issue.

This means ROUND can never be used in a central calc model. Instead you will always need to add it to the output module.

I asked them if there is any significant impact on performance doing so. In my case it would be > 200 line items using ROUND instead of 1, but total cell count is similar.

All comments

Misbah

@PhilippErkinger

Shouldn't be the case. Please share your findings here once Support gets back to you.

PhilippErkinger

Anaplan Support confirmed that it's a bug, but they are still looking into it.

Only workaround suggested so far is the old TEXT workaround used with ROUND before EXACT was available. My alternative would be to use a second ROUND() in the export module.

Both is not really "best practise" -> EXACT should just work.

PhilippErkinger

@Misbah I finally received feedback from Level 3 support. They gave me the following explanation:

This means ROUND can never be used in a central calc model. Instead you will always need to add it to the output module.

I asked them if there is any significant impact on performance doing so. In my case it would be > 200 line items using ROUND instead of 1, but total cell count is similar.

Misbah

@PhilippErkinger

Thank you so much for Sharing it. Appreciate that

Quick Links

Can you help?

Unanswered questions

Create a Filter to show all the elements of that level based on selection in hierarchy
Hello Community members, Requirement Details: I have 5 levels of composite hierarchy list (A1, A2, A3, A4, A5). I have published a module in UX, Now the requirement is If user select a list member from A4 level in the context selector or Custom Filter I have to display all the list members under that A4 level. How can I…
import monthly data with months in columns
is there a way to import data with months in columns (usual excel table view)? I have to transform the data so there are rows to cover each period in the upload data form, but I am wondering if there is a better way to just import the data as is with the months in the columns. please let me know what you think. thank you,
Cloudworks Big Query Integration Fail
Hello, I am receiving an 'Anaplan Upload Failed' Status Description when testing my integration with a Big Query dataset. The integration imports data from BQ to our Anaplan model. No other details given in the error log. I suspect that Cloudworks is not even picking up the file but am not sure what we did wrong on the set…