I'm running an ASP.NET 3.5 website that utilizes an SSRS 2008 report viewer control. I would like to utilize the built-in "Find" text feature, but am running into an issue where the report viewer frame within the page is loading the page itself.
When I navigate to the "report.aspx" page, the report is rendered on the page (in its own built-in iframe), and everything is good. When I enter text into the "Find" textbox in the report toolbar and click "Find", the first instance of the search term is found and highlighted in the report. So far so good. When I click the "Next" link, the "report.aspx" page is then rendered within the iFrame, which means that, now, in the browser, you see the report.aspx page, and then a window within showing the report.aspx page again, and then a window within that where you see the report viewer and the report itself.
Unfortunately, the "Find" feature is only available in Internet Explorer, so I built my own "custom" find feature for use in Firefox and Chrome. When implemented, Firefox and Chrome both exhibit the same behavior (report.aspx > report.aspx > reportviewer).
I've debugged down into the code, into the ReportViewer.js resource file, on line 421:
window.location.replace("#" + this.m_reportPrefix + "oHit" + this.m_nextHit);
This line is found in the "ReportFindNext" method. When this line is called, "window.location" is "http://localhost/site_name/Reserved.ReportViewerControl.axd?querystring_values_here", as expected. However, once the line is executed, somehow "window.location" becomes "http://localhost/site_name/report.aspx", and the iFrame then loads the report.aspx page, which results in the behavior described above.
So is there a way around this? Is this a known bug? What other options are there? We need to implement a "Find" text feature, and do not want to ask our customers to first export the report to Excel and do a search in there, if possible.
Thanks,
GH2