Query Studio Issue - Using Cube as data source

[vvasireddy9]

I am trying to create a query studio report with power cube as data source. The goal is to provide an interactive tool to the end users where they can drag and drop the data items they want to create detail report and define filters. The problem I am facing is with the available items structure. When a dimension is expanded, the parent is appearing twice/ appearing separately and each individual level repeating again like shown below.

---------------------------------- (In this hierarchy, 'Time period' is the dimension and it is appearing again above its levels when expanded)

Time Period
    -Time Period
    -Year
    -Month
    -Week

------------------------------------ (In this hierarchy, 'Run Date' is the dimension. It does not have any levels, it is appearing twice when expanded as 'Run Date' and 'Run Date1')

Run Date
    -Run Date
    -Run Date1


Is there any way I can have only the levels show under a dimension? Otherwise the users would get confused as two which item  to use (In the example below: Run Date / Run Date1)

[Lynn]

First of all, Query Studio is not "member aware" for dimensional sources so if you are on Cognos 10 then you really should consider using the new unified business authoring environment. This was called Business Insight Advanced originally but then renamed to Cognos Workspace Advanced in a later version. There are numerous other advantages that this tool offers over query studio.

Now that I've gotten that out of my system....on to your question.....

What you are seeing are the levels associated with each dimension. The level that is the same as the dimension name is probably best described as the "all" level or the top level of the hierarchy. It typically has one member which is the default member for the dimension, meaning (for example) that if you don't specify a time period, you get all time in your analysis. If you look at any of the Cognos sample cubes you'll see the same thing.

The modeler in your case didn't bother to explicitly name the "all" level and since you can't have two levels with the same name then it arbitrarily adds the 1 at the end. The Cognos Sales & Marketing cube has the order method dimension as a single level dimension, and there you can see they called the "all" level "Order Method" and used "Order Method Type" for the next level. Your cube designer should be able to correct the level names to avoid that confusion.

The rest is user education.