1.05-06 Only use Top Level for ultimate parent
Only use Top level for lists that will need sums so not Currency codes, or True/False (Indicators), or children in composite lists
Best Practices article:
Top Level Item and Parent Hierarchy
Comments
-
Rule 1.05-06 Only use Top Level for ultimate parent Only use Top level for lists that will need sums so not Currency codes, or True/False (Indicators), or children in composite lists
Here is how it was done in Pre Planual Era.
What is wrong with this method? It is not required at all. Because you are not going to aggregate the values based on all the currencies as the output won’t make any sense. Also the system will aggregate unnecessarily making that extra second delay impacting performance
Here is how it should be done in Planual Way:
As a thumb rule we don’t use Top level for lists that are not meant to be aggregated. Like currencies, Indicator lists or any other list which need not be aggregated.
0
Title
- Preface
- PLANS
- Planual Conventions
- Zen of Anaplan
- Chapter 1 - Central Library
- Time
- Versions
- Users and Roles
- Contents
- Lists
- Subsets
- Line Item Subsets
- Emojis
- Chapter 2 - Engine
- Modules
- Formulas
- Line Items
- Saved Views
- Chapter 3 - UX Principles
- Hierarchy of Information
- Smart Grouping
- Reduce Visual Load
- Progressive Disclosure
- Use Consistency and Standards
- Provide Help and Guidance
- Use The Correct Data Type
- Give Users Visibility Into Status
- Match With Real World Scenarios
- Check In With End Uses Frequently
- Chapter 4 - UX Build
- Apps
- Dashboards
- Filters
- Chapter 5 - Integration
- Actions
- Processes
- Source Models
- Imports
- Exports
- Import Data Sources
- Data Hub
- Chapter 6 - Application Lifecycle Management
- Revision Tags
- Production Lists
- Architecture
- Deployed Mode
- Managing Changes During Development
- Chapter 7 - Extensions
- Excel
- PowerPoint