Sunday 2 November 2014

Report Studio : Defect - Drill on MDX expression based members

Another one for the defect list and this in my opinion impacts a feature that is most important and that was working in earlier releases.

The defect relates to drill up functionality on MDX based lowest level members.

To re-create the issue:

Create an MDX based query calculation, say children of Cooking Gear.













Drill up on TrailChef Water Bag                                       










Drill up on Cooking Gear       
                                   







Drill down on Golf Equipment      
                                 







Drill down on Putters     
                                         






Drill down on Course Pro Putter 
                                   




Drill up on Course Pro Putter 109110         

                      











We see children of Cooking Gear (the list we started with) instead of Course Pro Putter.

Seems like the drill functionality in 10.1.1 has a lot of defects not just in Business Insight but in Cognos Viewer as well.

Limitation - Descendants MDX Function against Sets/Hierarchy

Though it is documented on the IBM Support Site that Descendants against Set functions may result in incorrect outcome, wish there was a way we could work around this limitation.

Some reasons why we may need Descendants function against a Hierarchy name rather than a member is:
When we use TM1 as the source and have security set up such that a user has access to the lower level members of a dimension hierarchy but not to the root member of the hierarchy (which is perfectly valid in our business scenario).
And we do not have named levels set up since we deal with unbalanced hierarchies, again valid when dealing with Accounts dimension.
And we have multiple alternate hierarchies set up against a dimension.

So in this case we are limited to using the descendants function against the hierarchy name rather than the root member which does not result in the required outcome.

So one of the work-around in this case is to use other MDX expressions like Descendants with Except to build the set required.

No comments:

Post a Comment