A new Method argument has been added to the end of the syntax for the ROUND function, with two available keywords: NORMAL and EXACT. NORMAL uses the historic rounding method, and remains the default behaviour if this argument is not provided in your formula. EXACT performs additional processing that minimizes the effect of floating point error in rare cases.
What does this mean for me?
You don't need to amend your existing models if you have not previously observed issues with your use of the ROUND function. Existing models (including currently archived models that you subsequently restore) behave as before, and return exactly the same values for formulas containing the ROUND function. No formulas are changed in your models. If the new Method argument is not specified, the NORMAL argument is assumed.
We suggest that you use the new EXACT argument for all new usages of ROUND in models you build.
For some use cases, you may prefer to use the new EXACT argument with the ROUND function instead of using the MROUND function. Specifically, if you currently use the MROUND function to round an input value to a power of ten (for example, the nearest 10 or 100), you can instead use the new EXACT method with the ROUND function. To do this, use a negative value for the number of decimal places argument. For example, rounding to -1 decimal places rounds to the nearest 10, and rounding to -2 decimal places rounds to the nearest 100. If you want to round a value to a multiple that is not a power of 10—for example, rounding to the nearest 12 or 300—then you should continue to use the MROUND function.
Upcoming product changes
In Q1 2020, we will be switching over the Anaplan landing page from "Launchpad" to "Home". All user access will be the same and users will be able to see only those models and New UX Pages that they have access to. See this Anapedia page about Home for more information about this new feature. Check out the Home release notes here for more information about the great benefits of the new Home page.
Issues resolved with customer cases
An incorrect number displays when importing data into a model where the First Data Row starts on or after the tenth row.
Unable to exportmodules with over 35 million cells to XLSX format,using the Tabular Single Column layout.
00237747 00254038 00257736
In certain circumstances, users will be unable to access Model History.
When an Application Lifecycle Management (ALM) sync is interrupted, the development and production models become incompatible and can no longer be synced.
A model that has a large number of list items and a module with nested dimensions could become unresponsive and display an error when you use Select Levels to show.
Questions, Comments, Kudos, or Concerns? Please comment below.