COGNOiSe.com - The IBM Cognos Community

Legacy Business Intelligence => COGNOS PowerPlay => Topic started by: cognosfreelancer on 23 Sep 2005 10:40:28 AM

Title: report does the disappearing act
Post by: cognosfreelancer on 23 Sep 2005 10:40:28 AM
Hello

I have a report that opens against a remote cube deployed on a PPES 7.3 server.

The client is 7.3 as well.

When I open a particular report, there is no data in it.

However when I drag in the relevant dimension from the dimension explorer to the columns areas of the report, the data reappears.

Seems some sort of a link is broken...

Any ideas...
Thanks
NKT
Title: Re: report does the disappearing act
Post by: Darek on 24 Sep 2005 08:16:12 AM
Was it after cube was rebuild?
Title: Re: report does the disappearing act
Post by: cognosfreelancer on 25 Sep 2005 07:54:51 AM
yes that is right. it was after a cube rebuild.
NKT
Title: Re: report does the disappearing act
Post by: dwood09 on 25 Sep 2005 10:25:27 PM
This type of thing could occur if you've got zero suppression on and there is no data for the report!

cheers,
DW
Title: Re: report does the disappearing act
Post by: GJParker on 26 Sep 2005 05:31:22 AM
This will happen if you change the name(s) of the dimenions which are/were on the report.

HTH
Title: Re: report does the disappearing act
Post by: Darek on 26 Sep 2005 08:19:27 AM
Or the categories change their category code.
Title: Re: report does the disappearing act
Post by: cognosfreelancer on 26 Sep 2005 08:51:47 AM
There was data for the report, as I was able to reproduce the report by dragging in the original dimension to the columns area


QuoteOr the categories change their category code.[

Hmmm... why would normally benign categories change their codes..

NKT
Title: Re: report does the disappearing act
Post by: Darek on 26 Sep 2005 11:03:23 AM
Say you are bringing in an unsorted query, where the same value repeats as source for different columns, which translate to different levels within two separate dimensions. IF those values, come in a different order on two different runs AND cube is build from a "clean and empty" model, than one of them is going to change it's value from "source" to "source~1", while the other will do the reverse.