Displaying Leaf Members of an Attribute’s Mapped Dimension

This feature allows you to display leaf level members of an attribute’s mapped dimension in views and reports. For example, let’s say you have an attribute called Product Type, which is an attribute of the Product dimension. Leaf level members of this Product dimension include; electric, single gear, and competitive. Within a view or report, you can now select the Product Type attribute and view the Product leaf level dimension members (electric, single gear, and competitive).

To enable this feature, access the Model task and the Attribute subtask. Select Yes for Enable Dimension Leaf Members as shown below.

Now, when you view the Product Type attribute in a view or report for the Expenses model, you can see the leaf level dimensions for the Product dimension. An example is provided below.

In the example above, ’20 inch’ is the product type attribute member whereas ‘B006742’, ‘B006813’, and ‘B006834’ are the product dimension members.

If Enable Dimension Leaf Members is set to No, the leaf level dimension members will not be available to view in a report or view.

In some cases, selecting Yes for Enable Dimension Leaf Members may result in a duplication conflict due to your naming convention for dimension and attribute members. For example, you might have a dimension named Sales in your dimension hierarchy. You might also have an attribute named Sales in your attribute hierarchy. This conflict may occur due to the attribute Member Code or Member Display Label. For the application to respond properly, you must change the Member Code or Display Label of the attribute.

To change the Member Code or Display Label of the attribute, access the Model task and the Attribute subtask. Select the Model, Dimension, and Attribute. Change the Member Code or Display Label and click Save.

When Enable Dimension Leaf Members is set to Yes and a duplicate is detected by the application, an email will be sent to the user. You can also view duplicate members, by accessing the Model task and the Model Validation subtask. The Model Validation page as well as the duplicate Sales Member Code (which is SALES) for the AllReportingResponsibility attribute is shown below.

The fields under the Duplicate Attribute Member Codes heading are described below.