Planual rules regarding Saved Views.
2.04-01 Give saved views meaningful names
| Give the saved view a descriptive, meaningful name that indicates its purpose (e.g., Build Departments List, Units Export, or Filtered View). There's no need to include the module name within the view name itself, as Anaplan automatically provides this context for you. Engine Applicability: Classic Hyperblock and Polaris |
bestPracticesArticles
2.04-02 Filtering on views
Filter on a Boolean and only have one filter per dimensional tab. Having multiple filters defined in the same tab can cause performance issues as Anaplan applies the filters sequentially (reads the data and applies the first filter, then applies the second filter to the returned set of the first filter).
bestPracticesArticles
2.04-03 Keep the Default View clean
| Ensure the default view is clean with no hiding, filtering, sorting, or conditional formatting applied as this can cause confusion and negatively impact performance by forcing the view to render unnecessary elements. In Polaris it's important to only use leaf-level selections in the default view also to avoid triggering On-Demand Calculation (ODC) of aggregate list members. Engine Applicability: Classic Hyperblock and Polaris |
2.04-04 Organize nested dimensions in order of size
| If you have to nest dimensions, always nest them in order of size from largest to smallest. Place the largest dimension on the outside and the smallest as the innermost dimension. Note: The Classic Engine supports nesting a maximum of three dimensions on rows or columns. Engine Applicability: Classic Hyperblock Only |
