If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Multidimensional Modelling

Started by Sunflower, 12 Oct 2010 02:28:19 PM

Previous topic - Next topic

Sunflower

Hi ,

I have created a Multidimensional Model with Regular Dimension and Measure Dimension.

My Regular Dimension is called Department.It has 20 levels .But ,the data is such that ,few levels will have same data repeated .

Is there a way ,that ,if the data in the levels are repeating ,the levels will not be showing.


Can anyone help me out.

blom0344

What do you mean with 20 levels? Don't you mean 20 distinct members in one level?
If that is the case then you need to assign a unique department key. If members repeat in the tree, then you did not assign the proper key

cognostechie

I think what he means is that the Dimension has 20 levels in the Heirarchy.

I don't think there is any direct way to skip a level in the hierarchy and go to the level below which has a different data. By the way, even if it could have been done, how would you know where you are once you start drilling down?

Maybe you could try calculations in Report Studio to determine the data value at the lower level and then use the 'set' function to get the values from the level below it and show it ...Not sure but try it..

blom0344

20 levels in 1 hierarchy.. You gotta be joking  :D   Take the known universe as a starting point and 20 levels would perhaps fit in.  But having 20 levels in a department?

cognostechie

His post indicates 'levels' in all 3 sentences and it is not an unusual scenario for the data to repeat in different levels. I would buy your theory that 20 levels in Department is un-imaginable but if he had only one level with 20 distinct values, why would he say that the data is repeating in different levels ?

blom0344

Assign the wrong key and you will be surprised how many duplicate values appear in the member tree. Only recently I goofed and assigned a key from an associated fact while correctly assigning the _MemberCaption from the dimension. Result: some 7000 members where only a couple of tens were expected..