Line Items: Are there excessive subsidiary views?
edited January 11 in Model Optimization Checklist
When is this a problem?
Subsidiary views should be avoided for data that is used in calculations.
The following are the situations where a subsidiary view can be used (note that they all are related to how the data displays):
- Show an attribute for end-user analysis, filtering, or sorting.
- Show an alternative hierarchy for a dimension.
- Display numeric values, such as ratios, that are not needed for other calculations.
- Filter reports or provide attributes for exports.
Why is this a problem?
Subsidiary views are hard to locate and audit in a model. If a line item with a subsidiary view is published to a classic dashboard, the data cannot be edited.
How to correct:
Think about adding a new module that includes the dimensions of the subsidiary view. See the Subsidiary Views lesson for examples.
Model Optimization Checklist
- Step 1 - Lists
- Does the list use Time as part of the key?
- Does the list use a combination of properties as a code?
- Does the list have a code?
- Does the list use Properties?
- Are there subsets on larger lists?
- Does the subset list follow proper naming conventions?
- Does the list include a top level when it is not necessary?
- Step 2 - Modules
- What dimensions are used in the module? Are they all necessary?
- What time dimensions are being used in the module? Can a Time Range be used?
- Are the dimensions in order?
- If there are any saved views, do they use the correct filtering?
- If there are saved views, are all of the line items in the view necessary?
- Is the default view clean?
- Step 3 - Line Items
- Which line items do not need a summary?
- Are text formatted line items overused?
- Are there more than 50 line items in a module?
- Are there excessive subsidiary views?
- Are there line items used as headers where the format is not set to No Data?
- Step 4 - Formulas
- Are there line items that can be placed in a systems module rather than within a calculation module?
- Are there any formulas that that combine text strings?
- Are there any formulas that are daisy chains?
- Are there long formulas, such as complex IF THEN ELSE statements?
- Is there an excessive use of the FINDITEM function?
- Are there SUM and LOOKUP combinations?
- Is the TEXTLIST function used?
- Do any formulas use the SELECT function, especially with time?
- Do any of the line items use conditional formatting with summaries turned on?
- Step 5 - Actions
- Are all the actions necessary?
- Do any of the actions result in errors when they are run?
- Check the data sources. Are some of them lists or modules?
- Check the data sources. Does each data source have an action associated with it?
- Step 6 - Time
- Is the main time scale of the model larger than it needs to be?
- Additional Resources
- Model Optimization Tracker