-
2.04-02 Filtering on views
Filter on a Boolean and only have one filter per dimensional tab Related to Rule: 4.03-01 Use efficient filters Best Practice article: Filter Best Practice
-
2.04-04 Nested Views
If possible, nest the dimensions in order of size (largest to smallest)
-
1.03-02 Performance and size can be dependent on the Users list
When Users list is heavily used, the number of users added can have a significant impact, be mindful of this and remove model access from any Workspace users when not required
-
2.02-12 No Hardcoding to List members
Avoid direct references to list item. E.g. IF ITEM(list)=list.xx. Instead, attempt to use a SYS module with a line item having a boolean format as this makes the formula more dynamic (multiple members can use the same logic).
-
5.01-04 Delete one off actions
For imports that are one offs, delete the import and data source
-
1.07-01 Naming Convention
Prefix with LIS: then a description or the module used in the Line Item Subset. For Line item subsets using multiple modules, use a generic name that best describes its purpose Related to Rule: 1.08-01 Don't use Emojis Best Practices article: Good Practice Naming Conventions
-
1.05-05 Format the Display Name property as a list if possible
Format the Display Name property for Numbered lists as List Formatted, not text. This is more efficient, saves a line item, minimizes text fields and simplifies mappings. However, it not recommended to create a separate list purely for this purpose; use an existing list if possible
-
2.02-10 Using PREVIOUS() vs CUMULATE()
For long timescales, using PREVIOUS is faster than CUMULATE due to the number of "reads" required for the calculation. So, the expression should be: 'Calc line item' = 'data line item' + PREVIOUS('Calc line item') rather than CUMULATE('data line item') Exception: 2.02-10a Short Timescales: Where the number of periods is…
-
1.05-08 Use Composite lists rather than ragged
Composite lists are more flexible and calculate more efficiently so try and "balance" the hierarchies whenever possible Exception: * 1.05-08a Chart of Accounts, or financial reporting hierarchies: Chart of Accounts, financial reporting hierarchies are valid uses of non-composite lists
-
1.07-03 Turn summaries off on Collect() line items
By default, you should turn summaries off on line items using the Collect() function. By having summaries turned on, the system is aggregating data that is not usually needed. Related to Rule: 2.01-10 Calculation Modules 2.03-01 Turn Summary options off by default
-
2.02-21 Don't use TIMESUM with Time
TIMESUM formulas should not be used in a line item that applies to Time, the formula will be duplicated for each time period. If the TIMESUM does use time periods then consider using MOVINGSUM instead. https://www.youtube.com/watch?v=PvimWuX5jVw
-
5.04-11 Use zip files for faster imports
Anaplan will accept a zip file format as an import source. For large files, this will greatly improve the import speed
-
4.03-07 Use notes to document line items used as filters
Make use of the notes section in the blueprint to document where a line item is used as a filter. This will help in the auditing of a model for saved views, and dashboard filters.
-
5.07-11 House a Data Hub in a separate Workspace
House the Data Hub in its own workspace. This allows for the data hub to expand in size without disrupting inbound or outbound integrations. It also allows for segregation of duties (users who manage the data, are kept separate from the production models)
-
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…
-
4.01-07 Use card templates
When utilizing the same module for multiple cards that are the same "card type", then consider saving it as a template. This will allow increased efficiency when creating boards or worksheets.
-
7.02-03 Version information
More information about versions can be found here. Version Information for PowerPoint Add-in
-
7.01-04 Version Informartion
More information about versions can be found here. Version Information for Excel Add-in
-
7.02-02 Define views within Anaplan to maximize performace
Try and minimize the amount of data you retrieve with the add-in in order to ensure great performance. If you want to retrieve a small amount of data from a large module, you might want to create a separate module just for the add-in Best Practice article Best Practices and Tips & Tricks About PowerPoint Add-In
-
7.02-01 Naming Convention
Do not change the module name in Anaplan as this may break the connection. Best Practice article Best Practices About Microsoft Office for the Add-Ins
-
7.01-03 Versions Control
It is best to upgrade to the latest version after it has been fully tested by the business Best Practice article Governance for the Office Add-Ins
-
7.01-02 Use Named Ranges in your formula
It is best to use Named Ranges rather than relying on formula references. Best Practices article Best Practices About Microsoft Office for the Add-Ins
-
7.01-01 Naming Conventions
Do not change the module name in Anaplan as this may break the connection. Best Practices article Best Practices About Excel Add-In
-
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-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
-
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…
-
4.01-06 Create Pages for Mobile
When creating Apps for mobile, think through the layout of the pages and develop the flow of page elements from left to right within each row on a Board. It may be appropriate to create a separate App for the mobile with proper spacing among the different elements Best Practice article Top 5 Design Best Practices for…
-
4.01-05 Use Worksheets for larger datasets
Use Worksheets for entering or editing large data sets, pivoting data Best Practice article Understanding Anaplan's UX with Analogies, FAQs and Best Practices
-
4.01-04 Use Boards for smaller datasets
Use Boards to render KPI’s, graphs, variance reporting, reviewing data from multiple modules, landing pages Best Practice article Understanding Anaplan's UX with Analogies, FAQs and Best Practices
-
4.01-03 Create Output modules when using Custom Views
When staging line items are not needed to be viewed by the page builder, create an output module to be used for generating the Custom View Related to Rule: 2.01-04 Use the D.I.S.C.O. Methodology for Module Design
