Add Mapping Rules for Derived Dimensions

Add Dimension Mapping Tables in Dashboards.

Security: Access Dashboards
permission.

Dimension mapping rules are the logic that tells Adaptive Planning which combination of mapping dimension values result in the derived dimension value.

Terms we use:

Derived dimension values: The dimension value that auto-populates on sheets.

Mapping dimension values: The dimension values that users select in sheets to trigger the auto-population of the derived dimension value.

Dimension mapping rules: The logic that maps the mapping dimension values to the derived dimension values.

Dimension mapping: The process of creating dimension mapping rules through dashboards or through dimension imports

Dimension mapping rules cause the derived dimensions to auto-populate on modeled sheets, saving time with data entry. When values auto-populate, the sheet displays a green triangle in the cell. The cell remains unlocked, so that users can select different values instead of the derived dimension value.

You can still make changes to the table from Dashboards. You can add the table for the same derived dimension to different dashboards. Any updates you, or anyone makes to the tables, persists to all dashboards. When you import new or updated rules, all the tables automatically update with the new changes.

If you enabled derived dimensions:

Before 2021R1, rules don’t automatically apply to child levels.

After 2021R1, rules at a parent level automatically apply to the child levels. You can still change the child level rules. To remove the automation, open a support case in the Workday Customer Center. See Contact Us.

Select

Dashboards

from the main menu.

Open a perspective.

Find a dimension mapping table. The dimension mapping table might have a specific name to help you identify it.

Select the appropriate version from the version prompt.

(Optional) From the mapping chart, click the Expand button.

To add a mapping rule, click the Add Row button.

Select a level from the drop-down in the first column. When you create rules for parent levels, the rule applies to all descendant levels. You can override this by creating a separate rule for child levels.

Select the mapping dimension values. Leaving cells blank for mapping dimension values means that the derived dimension auto-populates for any mapping value.

Select the derived dimension value.

(Optional) To switch the mapping dimensions of any 2 rules:

Select the check boxes in the 2 rows that you want to switch.

From the toolbar, click

Move mapping values between two rows

. The derived dimension values display as text boxes. The mapping dimension values display inside the text boxes.

From the

Dimension

prompt, select the mapping dimension. When you have 1 mapping dimension, it pre-fills for you.

From the text boxes, click a mapping dimension value.

Use the arrows to move between the boxes.

Click

(Optional) To delete rules, click the check box in the row and click

Delete

from the toolbar of the dimension mapping table. You must delete all the rules to remove the derived dimension capability from the custom dimension.

This example illustrates how child levels do or don’t inherit the dimension mapping rules of parent levels.

You have these levels:

Parent level: Engineering

Child level: Data Science rolls up to Engineering.

You have these custom dimensions:

Mapping Dimensions: JobCode with values: E2 and E3

Mapping DImensions: JobTitle with values Engineer, Engineer II, ML Engineer.

Derived Dimension: Job Seniority with values Junior and Senior

You have these dimension mapping rules:

Level	JobCode	JobTitle	Seniority	Explanation
Engineering	E3	Engineer	Junior	E3 and Engineer pre-populates Junior at the Engineering level.
Data Science	E3	Engineer	Senior	The same combination pre-populates Senior at the Data Science level.
Engineering	E2	Engineer II	Senior	Data Science inherits this rule because there’s no contrary rule in place for the combination.
Data Science	E2	ML Engineer	Senior	This rule is specific to the Data Science level.

These are the Job Seniority values that auto-populate for the Data Science level:

Job Code	Job Title	Job Seniority	Explanation
E2	Engineer II	Senior	Rule inherited from the Engineering parent level.
E3	Engineer	Senior	Rule created at the Data Science level.
E2	ML Engineer	Senior	Rule created at the Data Science level that overrides the rule specified at Engineering.

Build modeled sheets and add the mapping dimensions and the derived dimension. As a best practice, add the derived column after the mapping dimension columns.

When your team selects the mapping dimension values, the derived dimension auto-populates and the cell displays a green triangle. The cell remains unlocked, so your team can override the auto-populated dimension value. When they select a different value, the green triangle disappears so that you know it isn’t derived from the mapping values.