Why do we need a time setting module as system module when we already have a dimension of time?
I am a beginner in Anaplan so please pardon if my question is basic.
This lends to one of a key principle of model building calculate once reference many times. The system module allows you to define common attributes that will be refenced in downstream calculation modules.
The best practice for module design explains this in more detail:
https://community.anaplan.com/t5/Knowledge/Best-Practices-for-Module-Design/ta-p/35993
We have time dimension by default, But in order to use the calculations, we need to write some formulas and logic in the line items that are created in Modules. And a popular Anaplan saying, Calculate Once, Refer multiple times. That's why we create a module and as per DISCO, it has to be System module as it's common attribute that we will be using further as filter or in calculations in other modules.
Thank you for your prompt responses. This is very helpful!
It's now possible to use the additional insights to have dynamic filters, however the columns in the table are fixed widths. It's quite unfortunate that the ability is added, but the layout isn't dynamic. I understand that a report is more fixed, but adding dynamic columns would really help make the management reportβ¦
There was an error rendering this rich post.
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-yearβ¦
