Using Attributes in Maps for Metadata Transfer

You can copy Attributes along with their base dimension member mappings from a Source model to a Target model.

Each Attribute is associated with a dimension, and attribute members are mapped to the leaf members in the base dimension. You can copy both the attribute and the mappings from one model to another. This feature is not designed to transfer data from HACPM_Financial to analytic models.

• The Map must be of Type Metadata or Both.
• The Transfer type must be Leaf if used with map type Both.

When copying Attribute definitions and mappings, the following rules apply:

• The Target model must be cleared and regenerated as part of the process.
• The Source Filter Type can be AllMembers, LeafMembers, or MemberAndBelow.
• The Target Filter Type can be AllMembers, LeafMembers, or MemberAndBelow.
• Match Criteria Common is assumed, by default, on the row in the map that refers to the Attribute, whether you specify Common or not.
• Lookups are not supported for attributes.
• You can use variables and variable expressions with attribute and dimension member names.

The Attribute is created in the Target model and the dimension member mappings are copied for all dimension members that are common between the source and target.

If the Target model already has the same Attribute, its attribute hierarchy and mappings are deleted and replaced with the attribute hierarchy and mappings from the Source. The display labels originally assigned to the Target Attribute members are retained.

Example

The following example copies the attribute Olympics and its mappings on the base dimension Product from Detailed Revenue to My Cycles.

Here is a look at the attribute and mapping in the Source model.

Here is a look at the Product dimension in the Target model, My Cycles, before the calculation is run. My Cycles has another Attribute called Intended Use that is unrelated to the Olympics Attribute that will be copied. It has many product codes that are different than the products in Detailed Revenue.

A calculation clears the Target model and regenerates it. When generating a model, only one map for that model can be of type Both or Metadata. Because the map we created is of type Metadata, the GenerateModel step automatically runs that map to create and move the metadata from the Source model.

Here is a look at the Product dimension in the Target model after the calculation is run. The Attribute has been copied along with the mappings.