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

[RS] Aggregate Function Changes from None to Total

Started by jguevin, 15 Nov 2006 10:20:20 AM

Previous topic - Next topic

jguevin

Has anyone else seen this...we deployed a RS report from CRN 1.1 to Cognos 8 using the export/import functionality in Cognos connection.  However when we ran the report in C8, one of the measures showed as a cross product, upon further investigation in looking at the properties of that measure the Aggregate Function was changed from "None" to "Total".  This resulted in this report being very wrong!!  We also checked other reports that were migrated over and it happened to all of them, but the results were not incorrect.  In this particular case however, the cross product, was generated and the numbers way off.  Be aware that your reports could be wrong when doing this migration from 1.1 to 8 via the export/import functionality in cognos connection.  We started a case with Cognos on this and they are looking into it.  I will follow up here as well if I get an answer.  Thanks
Jeff

tdyoda

Yo Jeff!

We battle this constantly.  I'd like to join forces with your support case by linking my open cases with yours.  Post back if you're interested.

hendrixski

Oh my god, I lost 3 days trying to figure out what the hell was going on with a report... and then I tried some simple division inside of columns and it was coming up with random numbers.  I e-mailed my coworkers like "I think I found a bug" and they had no idea what was going on.  finally I realized it's the default aggregation setting being "TOTAL" rather than "NONE".

Why is that the default setting now?  Who thought that this would be a good idea?  Is there a way to change what it defaults to?

jguevin

sorry for the late response...this was put on the back burner for us.  Our case with Cognos was "parked"  based on code production issue 515407.  It is a known issue and a fix is in the works.  If you want to reference my case, the case number is 3383989.  Hope this helps.

Jeff