The web page loads fine but when you page through the report, the webpage does a postback, which I was thinking it shouldn't do since the report is sitting in an updatepanel. Should it?
Here is the code, just like the article here says:
<form id="form1" runat="server">
<asp:ScriptManager ID="ScriptManager1" runat="server" />
<asp:UpdatePanel ID="updatePanel1" runat="server" >
<telerik:ReportViewer ID="ReportViewer1" runat="server" Height="700px" Width="700px"
Report="RMSAnalyticsReports.rptIncidentDetail, RMSAnalyticsReports, Version=126.96.36.199, Culture=neutral, PublicKeyToken=null">
7 Answers, 1 is accepted
The ReportViewer control has its own mechanism for retrieving report pages. It uses an iframe to display the current report page and its content is populated by using a "get" request to a custom http handler which serves the requested page thus avoiding the postbacks to the page which holds the viewer. In this way all the requirements for the AJAX support are satisfied and additional roundtrips to the server and postbacks are avoided.
Because of this approach, however, you may see in the browser's status bar the "waiting for http://.. " message but this is not a postback. To be sure you can put a breakpoint in the Page_Load method of the page and see whether it is hit when pages are changed.
Hope this explanation helps. Let me know if you have any other questions regarding the issue.
the Telerik team
Thanks for the info. Then why when you page through the report without doing a post back, and you click the back button, it goes back through each of the pages instead of the page that called the report in the first place?
As I have explained in the previous post, the ReportViewer makes a GET request to the server in order to display the next report page. As such the GET request becomes part of the browser's history and when you click on the Back button it is repeated. The good news is that once loaded in the browser's session these pages are cached so no additional requests are made to the server. And yet, the lack of Back button support in Ajax technologies is usually identified as a shortcoming, not an advantage as you may read in the Internet. Let me know if I am missing your point...
the Telerik team
I supposed the same but there is no way to change this behavior with the current implementation. Still you can consider this as an advantage as you can see all the previous report pages you have viewed without any additional cost. After reaching the initial state of the viewer you will be able to navigate to the previous web page.
the Telerik team
I have a page with telerik:reportviewer. I don't want postback in report when I am changing pages from arrow of reportviewer. I have used Ajax panel to avoid flickering in report or postback but it is not working. Still page is getting postback.What i do for that, how can i fix this problem?
Please help me out of this problem .
Below i have attached code which i have tried:
All commands of the obsolete ASP.NET Web Forms Report Viewer are issued through an http handler and update only the report/report parameters areas and not the entire page.
There is no post back request made by the arrows for changing pages - AJAX support. Check for other elements outside the viewer that may trigger the post back.
It works in a client-server pair with the Telerik Reporting REST Service and does not make post back requests after initially loading the viewer.