2.01-11 Keep the Dimension Order consistent
Ensure the dimension order is consistent among modules. Calculations are faster if the common dimensions are in the same order as the Applies To. The size of the list is not as critical as the order Best Practices article: Dimension Order Questions on this topic? See 2.01-11 Keep the Dimension Order consistent in our…
2.01-12 Group formulas with like dimensionality
Create Calculation modules to house sets of line items that use the same dimensionality. Avoid using Subsidiary views Related to Rule: 2.01-06 Avoid using Subsidiary Views Best Practices article: Line Item Subsets Demystified Decreasing the Length of Your Formulas Questions on this topic? See 2.01-12 Group formulas with…
2.01-13 Separate Transaction data from Attribute/Property data
Keep the non-time-based data in a separate module from static attributes Best Practice article: Data Hubs Purpose and Peak Performance Questions on this topic? See 2.01-13 Separate Transaction data from Attribute/Property data in our Planual forum.
2.01-14 Avoid using Select Levels and filters together
Don't use Select levels combined with filters on the same hierarchy. It is a double filter and inefficient because both will be kicked off. Use one or the other. Setting a Boolean line item in a System module with 'none' as the summary option will often achieve the same result Questions on this topic? See 2.01-14 Avoid…
2.01-15 Filters in separate modules
Try and keep filters in separate System modules. They can then be reused for different modules. In the notes section, describe where and how this filter is used to prevent accidental deletion as the Reference By column will not list filters on views. Related to Rule: 4.02-02 Keep Filters in separate modules Questions on…
2.01-16 Use Data Tags
If not using for other reasons, use Data Tags to signify the DISCO category Questions on this topic? See 2.01-16 Use Data Tags in our Planual forum.
2.01-17 DCA Access Driver modules
Create separate modules for Access Drivers for relevant combinations to be reused. Use different line items for different settings if needed Questions on this topic? See 2.01-17 DCA Access Driver modules in our Planual forum.
2.01-18 Avoid copying large modules
Copying large modules, especially those with filters and many views, can take some time and block the model whilst doing so. For large modules, it is likely to be quicker to re-create the module Related to rule: 2.04-03: Keep the default view clean Questions on this topic? See 2.01-18 Avoid copying large modules in our…
2.01-19 Put Time and Versions list first in the dimension order
If you are using lists instead of native timescale or native versions, ensure these lists are placed as the first two lists in the dimension order. This mirrors the native time and version settings which will improve performance when mapping between native time/versions and standard lists Best Practice Article: Dimension…
2.01-20 Use Appropriate Dimensions for modules
When creating a module, consider the scope of the calculation and only include the dimensions that are needed. If the formula doesn't return the value required, or errors, don't keep adding dimensions until it does; it is better to review the calculation itself. Check other modules; you may already have a calculation…