Essbase internally constructs shortcut qualified names for members in duplicate member outlines. These can be inserted into scripts using Administration Services by right-clicking the member and selecting Insert member name. You can also manually insert shortcut qualified names into scripts, spreadsheets, or MDX queries.
Essbase uses the syntax shown in Table 14 to construct shortcut qualified names. Using the same syntax that Essbase uses when you reference members in scripts, spreadsheets, and MDX queries is optimal but not required.
Table 14. Shortcut Qualified Name Syntax
Scenario | Qualified Name Syntax | Example |
---|---|---|
Duplicate member names exist at generation 2 | [DimensionMember].[DuplicateMember] | [Year].[Jan] [Product].[Jan] |
Duplicate member names exist in an outline but are unique within a dimension | [DimensionMember]@[DuplicateMember] | [Year]@[Jan] |
Duplicate member names have a unique parent | [ParentMember].[DuplicateMember] | [East].[New York] |
Duplicate member names exist at generation 3 | [DimensionMember].[ParentMember].[DuplicateMember] | [Products].[Personal Electronics].[Televisions] |
Duplicate member names exist at a named generation or level, and the member is unique at its generation or level | [DimensionMember]@[GenLevelName]|[DuplicateMember] | [2006]@[Gen1]|[Jan] |
In some scenarios, the differentiating ancestor method is used as a shortcut. | [DifferentiatingAncestor].[Ancestors...].[DuplicateMember] | [2006].[Qtr1].[Jan] |