Defining the attribute dimension

In the attribute dimension, create an element for each dynamic attribute. Dynamic attribute elements can be string or numeric elements.

If there are multiple driver dimensions, they do not necessarily apply for all dynamic attributes. For example, the value of a product manager attribute for a product might be driven by time and by region but the value of a market entry date attribute might be driven only by region.

To control such different combinations of driver dimensions, add a boolean attribute in the attribute dimension for each driver dimension. The value, True or False, of such an applicability attribute determines if a particular attribute is affected by a driver dimension.

In the extended properties of a dynamic attribute cube, define, for each driver dimension, whether an attribute controls the applicability, and which element to use if a driver dimension does not apply.

The properties have these purposes:

  • DriverDimension: Identifies a dimension as a driver dimension.
  • ApplicabilityAttribute: Identifies which boolean attribute controls whether the driver dimension applies for an element.
  • NonApplicableElement: Identifies which element of the driver dimension is used if the driver dimension does not apply for an element.

For example:

… 
<Alea:DriverDimension Name="PERIOD"> 
<Alea:ApplicabilityAttribute Name="period_applicable" /> 
<Alea:NonApplicableElement Name="All Years" /> 
</Alea:DriverDimension> 
…

You must add the Format_Type attribute, although populating this attribute with values is optional. The clients can use the format string that you add to this attribute to format numeric attribute values. You can specify number formats, or name Application Studio styles, to apply when an attribute is presented in a report. For example, specify 0% to format 0.3 as 30%, or specify Currency to apply the number format of the Application Studio Currency style.