-
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.03-01 Turn Summary options off by default
Most line items in the model will not need summary calculations, so it is good practice to keep summaries off initially and turn them on only when necessary. This is especially true for Calculation modules and conditional formatting line items Exception: 2.03-01a User facing modules on dashboards: For Input or Output…
-
1.01-08 Daily Timescales on large timescales
Review the need for daily granularity for long timescales, specifically if the daily timescale spans five years or more. Use time ranges to restrict the daily calendars if possible and also use PREVIOUS rather than CUMULATE to optimise calculation efficiency. Related to Rule: 2.02-10 Using PREVIOUS vs. CUMULATE Best…
-
2.02-08 Never use SUM and LOOKUP together
SUM and LOOKUP used in the same expression generally cause large formula calculations and may cause intermediate relationship calculations especially if Time is a dimension or when the source and target structures are very different. Splitting them into different modules and line items considerably reduces the size of the…
-
Formula Break-Down Without Space Penalty
Currently, to adhere to best practices it is beneficial to break out parts of a complex calculation into separate line items for logic traceability and audit-ability. However, in many models we're constrained by space and can effectively reduce space (especially in large multi-dimensioned modules) by combining logic in…
-
1.06-02 Don't use subsets on large lists
Lists, and subsets take up space within a model, so if you need multiple subsets of the same list, consider whether they would be better as separate lists. This is especially valid if the lists do not overlap and they are being fed from a Data hub. For overlapping subsets or if there is a need to “consolidate” the value…
-
No of sums in a single line item
Hi, Need to know that how many number of sums we can use in a single line item so that its performance will also won't downgraded. Thanks, Vicky
-
Unlock Your Next Level Model Building Potential with Improved Anaplan DX
Hi Anaplan Community! I’m excited to present you Improved Anaplan DX by valantic, a Chrome extension, that also works seamlessly on Edge. This tool is designed to make your Anaplan model building experience smoother, more efficient and supercharge your productivity. Download the Improved Anaplan DX today to bring your…
-
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)
-
Repeated 'Illegal Argument' ERROR when pushing data through to a DataHub
I've been having an issue pushing large quantities of transactional data from an externally uploaded .csv file into a data module within a DataHub model. The .csv file is generated directly from an internal operational data store that queries data by client. I can populate its referential list with no issues which is the…
-
what would be the formula for referring Previous year value in current year ?
For example, I want to refer the value of last year july 2022 in current month July 23. the line item is Past year revenue where I just want to show same month revenue from previous year, how could I achieve that?
-
Ability to Apply Filters before downloading Model History
Currently, If I want to check history to view some activity on a specific module or list, but I am not aware of the dates when that change took place, It takes forever for me to extract the history for downloading 'ALL' change history and locate that change. I face issues especially when the changes are too many and file…
-
2.3.9.3 Update Historic Volumes for Baseline Forecast
I am having trouble adding a line item as my model has exceeded size. Here is what I am seeing on my screen.
-
Options to improve performance when loading flat list used in reporting
Hello, I'm loading flat data between 2 Anaplan models and in the target model, I'm using the Sum function to dimensionalize the flat data into a reporting module. The reporting module needs to have 5 lists + time and also requires summary to be on so data can be reviewed at aggregate levels. As a result the import action…
-
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
-
Model Optimization Checklist
As your Anaplan platform grows and continues to expand beyond your initial use case, it remains just as important as it did on day one to make sure your models are built to perform and according to best practice. Check out the model optimization checklist to begin evaluating your models today!
-
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
-
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…
-
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-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
-
1.01-07 Time Ranges
Use Time Ranges to optimize the modules where the default model calendar is not appropriate. Consider the dimensionality for the data and set up the Time Range accordingly. Best Practices article: Time Range Application
-
1.01-05 Exclude timescale subtotals by default
Turn the "include" settings off by default and only include these if absolutely necessary. These additional settings (Quarter totals, Year to date, Year to go etc.) will be included in all modules with the model calendar as the time dimension. Thus they will perform calculations on these subtotals. Consider if you really…