Essbase supports two different kinds of attributes, one called user-defined attributes (UDAs) and the other simply called attributes. A UDA is essentially any arbitrary “string-tag” that can be associated with any member from any regular dimension. A member can have multiple tags associated. The user can query to get all members of a dimension that have a specific tag (UDA). UDA-association of a member is also exposed in MDX as a dimension property of type Boolean as well. UDAs are displayed under the Member Properties folder of the associated dimension in the metadata tree view. When a UDA is dragged onto the design pane of the query designer, the generated MDX query automatically includes the associated dimension and puts the UDA onto the Dimension Properties clause of the query. There is no automatic aggregation of data to UDA values.
An attribute is more similar to a dimension property in the OLAP sense. Values for an attribute are collected in an attribute dimension, which may form a multilevel hierarchy similar to a regular dimension. Attribute values can be types of number, string, Boolean, and date. When an attribute is associated with a regular dimension, it appears under the Member Properties folder of the dimension in the metadata tree view. Drag an attribute from the Member Properties folder onto the design pane of the query designer and the generated MDX query automatically includes the associated dimension and puts the attribute onto the Dimension Properties clause of the query. An attribute dimension can also be selected on the Rows clause of the MDX query like a regular dimension. In this case, data is automatically aggregated from the associated dimension members to the attribute member.
Neither UDAs nor attribute values can be associated with calculated members. A request for a UDA associated with a calculated member always returns FALSE. Similarly, if you request for an attribute value related to a calculated member, you will always get NULL.
An attribute is more similar to a dimension property in the OLAP sense. Values for an attribute are collected in an attribute dimension, which may form a multilevel hierarchy similar to a regular dimension. Attribute values can be types of number, string, Boolean, and date. When an attribute is associated with a regular dimension, it appears under the Member Properties folder of the dimension in the metadata tree view. Drag an attribute from the Member Properties folder onto the design pane of the query designer and the generated MDX query automatically includes the associated dimension and puts the attribute onto the Dimension Properties clause of the query. An attribute dimension can also be selected on the Rows clause of the MDX query like a regular dimension. In this case, data is automatically aggregated from the associated dimension members to the attribute member.
Neither UDAs nor attribute values can be associated with calculated members. A request for a UDA associated with a calculated member always returns FALSE. Similarly, if you request for an attribute value related to a calculated member, you will always get NULL.
No comments:
Post a Comment