The custom ReportResolver is called multiple times while displaying the report - on initial loading of the report, on consecutive interactions as export, print, parameters changes. The custom ReportResolver is called also on changing the viewer's Report property in code. Thus consider caching any data retrieved in the custom resolver to avoid the consecutive calls to the data if they are not needed. Check my colleague's example here
About switching to the HTML5 Report Viewer, it works with the Reporting REST service - HTML5 viewer overview
. The service allows you to use your own custom resolver
, where the custom resolver's Resolve method is called multiple times again on initial displaying of the report and on consecutive interactions with it in the viewer.
Note that both Reporting WCF and Reporting REST service purpose is to deliver content from the server to the client, where the server uses the same reporting engine to resolve and generate documents. When you use custom logic for resolving reports, it must be considered with the technology.
You can test the performance of the Reporting WCF and Reporting REST services with the local demos, installed by default under C:\Program Files (x86)\Telerik\Reporting <VERSION>\Examples
Let us know if you need any further help.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items