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

Cognos 10.2.1 different from Cognos 8.3

Started by dbahiker, 06 Sep 2013 07:40:51 AM

Previous topic - Next topic

dbahiker

I have a report with a crosstab and we have noticed that Cognos 10.2.1 is not getting the same number at Cognos 8.3.
Data is the same. It's the running difference function that is off.
Should or wanting to be Volume 400 for 11/30/12  - volume 200 for 10/31/12 = 200 MTD Growth

Expression is: running-difference([Loan Volume])

Loan Volume expression:  is a dollar number

I want the running difference for columns not rows.

                           09/28/12 | 10/31/12  | 11/30/12

Volume                  100       |         200   |      400

MTD Growth          NULL     |        100     |      200   

Lynn

Why, why, why, why, why would you post your company's sensitive information on a public site like this???

dbahiker

because the numbers are made up!  :P

blom0344

Did you check whether the 8.3 and 10.2 query have the same SQL ?  The running totals are computed on the server, so if the SQL is the same, this may point at a 10.2 bug. 
Personally I would not post report images containing whatever data on a public site.  The image can turn up anywhere without your comment about the randomness of data. And then who would know whether it's 'real' or just 'fake' data ?

CognosPaul

We've had a few cases here of people posting private information, so we tend to be overly cautious when it comes to data with company names attached.

Is this relational or dimensional? Are you running DQM? Is the volume measure a calculated field, or a normal cumulative measure from the data source? What happens if you set the solve order on MTD growth to 2?

dbahiker

#5
I have removed the image.

Relational
No DQM
Volume measure is a calculated field
When I set the solve order on MTD growth to 2 I get the same results.

CognosPaul

#6
As a test try replacing the field with a normal cumulative value. My guess is that the calculation is getting messed up somewhere. At worst you can put the running difference in a derived query.