Many OLAP technologies offer the ability to have a member property, with the same name, spanning multiple levels. At the moment there is no good way of getting that common attribute into a report when building a mulit-level set.
I may have a set expression like this:
descendants([Level1],1, self beforewithmember after)
I would like to be able to use roleValue('ShortName',currentMember(hierarchy))
This should let me show the ShortName for each member in the crosstab rows, regardless of the level.
At the moment when I do this I get the following error:
XQE-PLN-0266 The query contains a role value function with an invalid first argument: 'ShortName' is not a valid role or property.
This is because the MDX validator is automatically failing roleValue expressions against multi-level set.
The MDX that's generated against a single-level set:
DESCENDANTS([R_PRODUCT].[R_PRODUCT].[Level1], 1) DIMENSION PROPERTIES PARENT_LEVEL, PARENT_UNIQUE_NAME, [R_PRODUCT].[ShortName] ON AXIS(0)
works, an I would expect a multi-level set to work exactly the same way:
DESCENDANTS([R_PRODUCT].[R_PRODUCT].[Level1], 1, SELF_AND_AFTER) DIMENSION PROPERTIES PARENT_LEVEL, PARENT_UNIQUE_NAME, [R_PRODUCT].[ShortName] ON AXIS(0)
This is especially frustrating in a TM1 environment where the member properties that DO work (alias, description) have a uniqueness requirement that prevents it from working.
I personally believe this is a bug in the product, however I was instructed to open this as an RFE.
|Who would benefit from this IDEA?||At the moment report authors have NO way of building this output. So both report authors and consumers will benefit.|
How should it work?
My solution is to change the validator to throw a warning when this happens. Let the cube throw the error if it's not actually valid. This is an example of Cognos incorrectly thinking that it knows better than the developer.
|Priority Justification||This is ranked urgent because I have required reports which I am unable to provide without significant work-arounds.|
|IBM's success depends on gathering feedback from customers like yourself. Aha Ideas Portal is the third party tool through which IBM Offering Managers gather feedback from customers such as yourself.|
|IBM is a global organization with business processes, management structures, technical systems and service provider networks that cross borders. As such, the information collected through Aha Ideas Portal (Customer Name, Customer Email Address) will be stored by them in the United States, and handled only as per IBM's instructions and policies. Your data (Name and Email Address) will NOT be shared with other IBM customers.|
|In order to safeguard your information in Aha, do not leave your workstation unattended while using this application, log off after using it, and print only if necessary. If you need to make a hardcopy, remember to pick up the print-out immediately, keep it under lock, and destroy it immediately when no longer needed.|
|NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions|