1.06-03 Avoid single item subsets
If possible, try and avoid single item subsets, if there is a top level in the list, a single item subset will always have two members. Consider using a Boolean flag in a SYS module or a LOOKUP line item against the desired item (to avoid using SELECT)
Comments
-
Rule 1.06-03: Avoid single item subsets If possible, try and avoid single item subsets, if there is a top level in the list, a single item subset will always have two members
Here is how it was done in Pre Planual Era. We used to create a subset which includes/houses just a single list item
List:
Input module:
Output module:
What is wrong with this method? Item which was supposed to be just one has become two because it will have top level coming along with it.
Here is how it should be done in Planual Way: Can be done in many ways. One way could be with the help of LOOKUP module. Get rid of the subset dimension and use LOOKUP on the ssAsia or Region formatted line item
Output Module
LOOKUP module:
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