The Zen of Anaplan
The Zen of Anaplan
Ten guidelines
• Just because you CAN doesn’t mean you SHOULD
• Calculate once, reference many times
• Simple > complex
• Only calculate when you need to
• Sparsity is not your enemy
• Big and fast > small and slow
• Booleans = great. Text = bad
• Text joins = worse
• Don’t let exceptions overcomplicate the model
• Sums and lookups are good, but never together
Comments
-
Hi @rob_marshall, can you expand upon "sparsity is not your enemy?"
Thanks
0 -
Hey @Olek P
Sure thing…People try to create all kinds of logic within one line item to save space (or make it more dense), but in reality, that is doing the calculation engine an injustice because the formula does not get kicked off once, but rather once for every cell defined for that line item. It is better to create calculation modules, while they may be sparse, do to the calcs because they will be faster for the engine to process because the logic is doing less.
Take a look at these articles that Dave Smith wrote several years ago.
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