-
1.02-01 Use "Current" in Version settings
Utilising the Current (and Actual) check box within the Version Settings allows the use of CURRENTVERSION() and ACTUALVERSION() in calculations, in SELECT statements and ISCURRENTVERSION and ISACTUALVERSION() for Boolean checks. Current version also acts like a top level for Versions; if you have a source module with…
-
1.02-02 Do not use formulas in the version settings
Whilst this is a simple construct and it might be OK for simple models; it effectively adds size to models every time versions are used in a module even if you don't want the variance. Also, in modules with 3 or more dimensions if you have calculation line items and aggregations the results may not always be give the…
-
1.02-03 Edit To / Edit From
Use these as a simple, administrator lead control for read and write access to versions. For more granular control use Dynamic Cell Access Questions on this topic? See 1.02-03 Edit To / Edit From in our Planual forum.
-
1.02-04 Always move switchover dates forward
Using switchover means the historic periods are effectively cleared out. This does have the benefit of reducing model size as the historic cells are cleared, but switchover should be moved forward only. Moving it backwards will blank out the respective period removing any values that were previously held Questions on this…
-
1.02-05 Try and avoid a high number of native Versions
Versions have built-in functionality that is not available for normal lists. However, a large number of Versions (e.g. 10+), can have performance implications due to the block structure. Review the need for high number of Versions, and if the native functionality is not critical or needed, consider using a normal list to…