Feature Overview
When managing data imports, wrangling, or adding new members to a model dimension, you can mark specific properties or parent-child hierarchy nodes as mandatory. This ensures that essential data fields are consistently filled out and complete.
Benefits of Enforcing Mandatory Properties
Enforcing mandatory properties helps you:
- Maintain Data Consistency: Ensures that all critical information fields are consistently filled, ensuring uniformity across your dataset.
- Guarantee Completeness: Keeps essential information intact and prevents gaps, supporting data accuracy and reducing the risk of errors during processing.
With this approach, your data management becomes more streamlined, reliable, and ready for confident decision-making.
How to Flag Properties or Hierarchy Nodes as Mandatory
1
Identify the Property or Node: Decide which properties or nodes in your data hierarchy are crucial and should always have values.
2
Set the Mandatory Flag:
a) Apply a “Value is mandatory” status to the chosen properties or parent-child nodes.
Example: Create a new mandatory hierarchy
Image 1. Fill in ID and check the mandatory box
Image 2. The hierarchy becomes mandatory and force user to input data
Image 3. The warning disappears after inputting a <root> node
2
Set the Mandatory Flag:
b) For parent-child hierarchies, if a specific parent isn’t provided, the system will default to using the root node (<root>) as the placeholder.
Images 4 and 5. Importing master data and map hierarchy field, blank cell will default to the <root> node
Image 6. Final result.
3
Enforcement: Once flagged as mandatory:
a) The system will enforce this requirement during data import.
b) Data wrangling processes will respect this mandatory status, ensuring no missing information slips through.
c) When new members are added to stories, they must meet this requirement, maintaining data structure integrity.
4
Leverage for level-based hierarchy.
Since level-based hierarchies are built from properties, making these properties mandatory will enforce completeness within each level, similar to how it works for parent-child nodes.
Setting a Property as Mandatory
Setting a property as mandatory is indeed similar to the approach for parent-child hierarchies. Here’s a step-by-step guide:
a) Identify the Property: First, select the property that needs to be consistently populated. This should be a property crucial to the data structure or integrity, just like nodes in a parent-child hierarchy.
b) Apply the Mandatory Setting:
- On the Details panel, click three dots > Edit > Toggle “Value is mandatory”.
- Once set, this requirement will ensure that all instances within the level-based hierarchy have values for that property, reinforcing data completeness.
c) Enforcement Across Processes: Just as with parent-child hierarchies, setting a property as mandatory will apply to data import, wrangling, and the addition of new entries. Any missing value will prompt an alert or require completion before proceeding, preserving data accuracy.
