MR3 Changed the query

[cognosguru]

Has anyone upgraded to MR3 yet?Ã,  We are in testing phase and some of our reports are now producing very different sql and run a lot longer.Ã,  If anybody ran into this issue please let me know.

Thanks,

:o

[cognosguru]

The problem is with the way MR3 is handling a calculated field, (field with aggregation set to calculated) that has if then else logic built into it.Ã,  In MR2 you could pull that field from the model and aggregate it further (by groups).Ã,  In MR3 that doesn't seem to work.Ã, 

The workaround used was to pull into the report components that would make up the calculation and performing it at the report cube level.

There was one more issue with utilizing multiple columns for sorting purposesÃ,  for a grouped column.Ã,  For instance, if Product Type is grouped, I also have Product Type Sort Key (sorted) column above it in the level, and Product Name to further sort it.Ã,  In MR2 that worked, in MR3 it doesn't.Ã,  Looking into solutions now.Ã,  Will update when have one.

Allen.