ReportViewer Html5 Toolbar does not work after upgrade to v9

[Fernando]

Hi guys, I have an asp.net mvc application and we are using the telerik reporting for html5. 

 We have some old applications using the v8 of Telerik Reporting for Html5 and it is working fine. So, in a new project we updated to v9 (9.0.15.324) and when we render a ReportViewer, the toolbar buttons does not work properly. We can export and page manually (typing the number of the page and pressing <enter> key), but buttons like "first", "previous", "next", "last", "zoom in", "zoom out",  "filter", etc... does not work. all javascript and css files for reportViewer are included on page and the render is ok, but the toolbar not.

 I tried to check the the console of the browser but when we click on a toolbar's button, there is no message on the console. I also tried to add the following module on the web.config as this thread, but it didn't work.

 <modules>
  <remove name="UrlRoutingModule-4.0" />  
  <add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="" />  
</modules>

 

Is there something I can try to make it work?

If there is no solution, we will back to v8.

 

[Piotr]

Hi,

We have exactly the same problem here.

[Stef]

Hello,

After installing the new version of Telerik Reporting you need to run the Upgrade Wizard in all related projects having references to Telerik Reporting.

Also it is recommended to download and install Telerik Reporting Q1 2015 SP1 internal build 9.0.15.422 where we addressed several issues related to the service's cache management. The internal build can be downloaded from your Telerik accounts - Products & Subscriptions - Latest internal builds, where you need to select Reporting as a product, and if you have previous downloads, the current major version which is 9.0.15.324. As a result the page must be reloaded and you will see a download link for version 9.0.15.422.

Other steps to troubleshoot the problem are to:

• Check if you have loaded jQuery only once on the page. Having jQuery loaded multiple times or/and of different versions may causes issues on creating the viewer;
• Check if you have loaded Telerik Kendo UI CSS and JS file on the page only once and from the same version. Mixing the versions of Telerik Kendo UI CSS and JS files may lead to malfunctions of the viewer;
• Check if the Reporting REST service's routes are not duplicated with other routes in the application.

The recommended troubleshooting approach when using the viewer is to use the browser's Console or download and install Fiddler. In Fiddler - Inspectors - Request/Response - Raw tabs will be listed information about the made request and its response, including a list of all performed requests for the page.


If you need further help, please send us the SAZ file with the recorded requests and demo projects illustrating your settings. For the purpose you will need to open private support tickets, where ZIP attachments are allowed.

Regards,
Stef
Telerik

[Piotr]

We found the reason of problem. You are using this.selector from jQuery in widget's initialization. selector property is deprecated and according to documentation it is removed (https://api.jquery.com/selector/) , but it still exists in new versions. Unfortunately, in some situations, jQuery returns empty value, which makes widget unusable.

[Nasko]

Hello Piotr,

The issue is now logged in our system for improvement and your Telerik points are updated in order to thank you for the provided information.

Regards,
Nasko
Telerik

[Luke]

Is there a time frame for fixing this issue? The problem is not that selector is deprecated. The issue is that the report viewer code assumes that it will always be initialized with a css selector rather than a dom node. Given the way it is written even when using a css selector, If you had multiple matching nodes, the buttons on one report viewer would probably affect the others. 

[Nasko]

Hello Luke,

All of the provided information on the issue has already been logged in our bug-tracking system. We will address the issue in a future release of the product, but we cannot engage with a specific time frame for the fix. You can follow our Release History page to get updates on the latest fixes and changes in Telerik Reporting.

Regards,
Nasko
Telerik