2.01-16 Use Data Tags
If not using for other reasons, use Data Tags to signify the DISCO category
Comments
-
Rule 2.01-16 Use Data Tags If not using for any other reasons, use Data Tags to signify the DISCO category. It doesn’t go against any element of PLANS but why not use it when we have the functionality available.
Use Case: As a workspace admin I need to check if ALL Countries are available in multiple lists within the model. (Countries are mentioned in multiple lists, hence need to audit). I need to check if employees have the countries field populated.
Here is how it was done in Pre Planual Era: We used to search the lists one by one. Go to modules, apply filters and on line items to check for Blanks. Imagine the amount of effort and pain that one has to go through in doing so. Let’s say I have to search if Japan is listed in both my lists. I will also the employees who work from Japan
Step 1: Go to Country List and Search
Step 2: Go to Second list and Search
Step 3: Go to Module -> Country Line item-> Apply Filter on Japan or Blanks
Another example can be employee hierarchy where same employee can be in multiple lists
What is wrong with this method? Nothing wrong, it is just time consuming
Here is how it should be done in Planual Way: This feature helps in quick searching and grouping of various artifacts like Lists, List Properties, modules & Line items. This is like search engine within Anaplan that will save you a lot of time when you want to search for List Items and List or Text formatted Line items and Properties. If it is Number formatted it will be excluded from the search. Once Data tags are created, artifacts tagged you can find the tagged data by clicking on “Find Tagged Data”.
Let’s see how we can find Japan without going to multiple lists
Step 1: Create a data tag of Countries.
Step 2: Tag the required lists. I have tagged Country list, Child list & Employee List
Step 3: Go to Data Tags and Click on “Find Tagged Data” & search by typing the text (case Insensitive)
Result: All the search results across the model will be displayed in one single window. Be it list items, list properties or module line items provided these are list or text formatted
Note: Data Tag is a workspace admin feature
2
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