Report Studio Oddity

[UcfMike]

I have a report which has 3 query calculations which are nearly identical.

round((maximum(running-count([Unit Name] for [Resort Name],[Frequency],[Inventory Status Name]))/[Weeks to Interests]),0)

The only difference is that I add an extra query subject to the for statement for each of the other query calculations.

Here is what is happening. I add the first query calculation and group span it to the correct column, everything works fine.

I add the second query calculation and group span it to the correct column, everything works fine.

I add the third query calculation and group span it to the correct column, and it works fine, but the previous two query calculations now take on the top value of the third query calculation. At some point I've been able to stop this from happening by breaking apart the third query calculation into multiple query calculations, or by naming the third query calculation something obscure like 'Bob'. At this point, those things are not working either.

Has anyone come across something like this?

 

[sln007]

No, haven't come across that.

I'm wondering why you would use
"maximum(running-count([Unit Name] for [Resort Name],[Frequency],[Inventory Status Name]))".

I use a separate query calculation as
"count([Unit Name] for [Resort Name],[Frequency],[Inventory Status Name])".

I know there are various ways of accomplishing the same thing, but trying to keep everything as simple as possible usually helps too.


Steve N.
State of Ohio, MIS

 

[CognosProfessional]

Have you tried seeing results with different choices in the "Before aggregation" or "After Aggregation" properties?

CP