To use Cognos product documentation, you must enable JavaScript in your browser.

Recommendation - Use Member Unique Name (MUN) Aliases

If you are working with a dimensional data source, use MUN aliases to simplify building reports and expressions. In addition, you can tie the MUN back to the member in the package.

When working with dimensional data sources, Cognos 8 uses MUNs to uniquely identify members. MUNs are very complex. For example, the MUN for the member 2004 might appear as follows:

[great_outdoors_company].[Years].[Years].[Year]->:[PC].[@MEMBER].[20040101-20041231]

When you are building expressions that involve members, the use of MUNs makes these expressions difficult to read and maintain.

Tip: To view the MUN of a member, in the Insertable Objects pane, on the Source tab , right-click the member and click Properties.

Report Studio has an option that automatically generates an alias for MUNs . The MUN alias is a data item that has the MUN as its definition. For the previous example, you would see 2004 as the data item, and the MUN would appear in the data item’s Expression property. Enable this option to produce a MUN alias whenever you add a member to a report or expression.

Note: Do not modify or rename MUN aliases, because they will lose their connection to their respective members in the package.

Running a Report That Contains Members

If you are using members in a report and your modeler has updated the data source in a way that changes member unique names, the following problems may arise when you run the report.

To resolve these problems, you must update the member unique names in the report. Open the query that contains the members that you need to update in Query Explorer. Delete the member from the pane in which it appears and reinsert it from the Source tab. For example, if you inserted the member as a detail filter, delete it from the Detail Filters pane and reinsert it.