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

Drill-through Report Displaying Cached Results

Started by pacificbeavs, 21 Aug 2018 10:31:52 AM

Previous topic - Next topic

pacificbeavs

I have a parent report, and it drills through to a child report.

In 11.0.7 you can drill through to a child report, hit the back button on the browser, and then drill through on a different item and get new results in the child report.  However, we upgraded to 11.0.11 and now when you go back, and then drill through again you get the same presumably cached results as the initial drill through.  The only solution appears to be setting Run with Interactivity to "No", which then allows you to go back and drill through on a new item.

Any other ideas on how to get around this, without having to set the interactivity to "No"?

Thanks!

Penny

Perhaps try changing the property of the query in the called report for 'use local cache'...set it to no.

Robl

It might be the browser cache.
That's nothing to do with a Cognos problem.

It may be worth setting the drill report to open in a new tab, then the user can close the tab and select a new drill.
Or can tab back and have multiple drills open at the same time.

I always try and avoid using the "Back" button as part of my report functionality.

pacificbeavs

Quote from: Robl on 22 Aug 2018 05:37:19 AM
It might be the browser cache.
That's nothing to do with a Cognos problem.

It may be worth setting the drill report to open in a new tab, then the user can close the tab and select a new drill.
Or can tab back and have multiple drills open at the same time.

I always try and avoid using the "Back" button as part of my report functionality.

Thanks - opening in a new window appears to do the trick, and eliminates the need to go "back".  I'll move forward w/ that solution.

Unfortunately the local cache set to "No" did not fix the issue, and I don't think it's the browser because it still functions in our production environment (which is still 11.0.7).