If I run 2 separate reports, then click the browser's back button, I am returned to the first report page, but the report does not display. I get a display of the reportviewer with empty report parameters. I don't think the product used to do this.
BTW, this happens with IE8, but not with Firefox 3.5.11.
Any ideas? Thanks.
Dan
5 Answers, 1 is accepted
We are not sure we have correctly understood your inquiry.
If you are after Drillthrough reports, note the page is actually the same and in fact the content within the Web Report Viewer frame is the only updated part. Thus for the drilltrough functionality our suggestion is to use the report viewer's history (back and forward) buttons.
Peter
the Telerik team
Rank 2
This is not a drillthrough report situation. The two reports I am talking about are both Telerik Reporting reports, but they are completely separate report pages.
User runs the first one. Then user navigates to second report URL. Then user clicks the browser back button, and first report fails to render, showing only empty reportviewer controls.
Dan
Locally we used both IE 8 as well as latest version of Firefox and we could not reproduce the problem - check out the attached video. In this line of thoughts, we would appreciate if you provide us with a sample project that exhibits the problem.
As an alternative, our suggestion is to use the drill-through functionality and report viewer's history buttons for navigation between reports in a single viewer if applicable for your scenario.
Peter
the Telerik team
Rank 2
It would be pretty difficuult for me to set up a sample project that demo's the problem. But, I would like you to see the problem, which you could do, if I gave you access to our internet/demo instance of our product which is exhibiting this problem.
Could I send you this access offline from the forum? I cannot have this published in the forum.
Thanks.
Dan
Even if we see the issue, we will not be able to help you without the project itself. Because we're both unable to reproduce the issue, this lead us to a conclusion that you have a web form code that alters the session or something else that influence the browser's history.
Kind regards,Peter
the Telerik team