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

Icon - could someone tell me what it is, or stands for

Started by andyhofer, 26 Jan 2010 10:58:09 AM

Previous topic - Next topic

andyhofer

I have a report that includes a query and under data items on the right hand windows is an item against one of the data items.



Could someone tell me what this little icon / symbol stands for or represents.

Thanks

mgibson

Its' probably representative of the type of aggregation used.

Mick

MFGF

By the looks of it, this item is a level from a dimensional hierarchy in the package.

MF.
Meep!

andyhofer

Thanks for the responses, I'm having trouble with this because it currently has a dimension in it that is for months, but I would like to change the report to weeks, but no matter what I try I cannot edit the data item to change it to weeks or create a new one from scratch.

Andy

MFGF

Assuming it's the Month level from your time dimension, you should be able to simply drag the Week level into the report in place of the existing Month level, then delete the Month level.

MF
Meep!

andyhofer

Yep, I agree, but I cannot find a week level in the package and was looking to create one, but I cannot seem to be able to do this and get the same effect. I dragged on the week level available that has a different icon to the one questioned and it shows all the weeks but for some reason only populates the first week with values.

So I thought, I'll create the weeks using the same method as that for the months, but I can;t get the same effect or the same icon next to the data item. I assume the icon is placed by the system based on the type of data item created, which is why I asked what the icon meant so I could then recreate the same for weeks.

Hope this makes sense

Andy

MMcBride

Quoteno matter what I try I cannot edit the data item to change it to weeks

I am not sure if this will help but this part of your post jumped out at me.

Occassionaly within Report Studio using a Cube based source I have seen reports where you could not edit a Data Item.

If you look at the properties for the Data Item you will see that some Properties are missing.
Aggregate Function, Rollup Aggregate Function, Pre-Sort - if all of those and more are missing then you are seeing what I have.

If not then its not related and you don't need to read further :)

I am not sure exactly how this is caused as it was created by one of my End Users. In Report Studio go to File > Report Properties.

You will propbably see a Box selected with the label "Always create extended data items" selected

Deselect this box and try to create your report again.
You may have to recreate the report from scratch, as I have found some reports that were unaffected by deselecting this option. But on some this allowed me to once again be able to edit these Data Items.

On the First report I tried to fix though nothing I do fixes this problem. But if I make sure the box is unselected then create the exact same report using the same data Items I am able to edit them and customize them the way I want.

I hope this helps







MFGF

Quote from: MMcBride on 28 Jan 2010 11:37:28 AMI am not sure exactly how this is caused as it was created by one of my End Users. In Report Studio go to File > Report Properties.

You will propbably see a Box selected with the label "Always create extended data items" selected

Deselect this box and try to create your report again.

Hi,

In Cognos 8.1 and 8.2, all items (query items, hierarchies, levels, attributes, calculations etc) were treated as expressions, and were therefore difficult to distinguish between visually when viewed in the query.  From 8.3, this behaviour changed, and objects such as levels, hierarchies etc are no longer treated as expressions by default, and have a different icon to mark them.  The old 8.1/8.2 behaviour can still be implemented using the steps you detail above, but this is not the default behaviour out-of-the-box.  The alternative is to drag in a Query Calculation and populate this with your level/hierarchy etc in order to obtain an expression which can be edited later.

Regards,

MF.
Meep!