7 Answers, 1 is accepted
You can easily change and customize the toolbar of the Report Viewer (assuming from your other question that you will be using the ASP.NET Report Viewer). For more information about the possibilities and how to do that please check this Custom Toolbar for the Web Report Viewer.
All the best,
the Telerik team
Have you tried the new visualization options in Telerik Reporting Q1 2013? You can get them from your account.
What about customizing the HTML5 Report Viewer? I want to be able to:
- hide some of the buttons
- change implementation of existing button -> i.e. custom "Export to CSV"
- add new buttons with custom implementation
I see it's using an html template, but I haven't figured out how can I do the above (beside removing buttons and changing order on the toolbar).
If you are using the HTML5 Viewer, you can make a copy of the viewer's HTML template file and modify it. Then set the viewer's TemplateUrl to point to the modified HTML file.
If you need to add custom export options, hide the default export buttons and use your own UI. To handle the default export options, you can use the HTML5 Viewer's API:
I hope this information is helpful.
Thanks for your help! I will give it a try :).
I'm using the HTML5 Webform ReportViewer in a webforms app and trying to remove some buttons.I have:
In ~/ReportViewer/templates/telerikReportViewerTemplate.html (which I've confirmed is loading) I've removed:
from the trv-report-viewer and trv-content-wrapper k-content classes but the buttons still appear. I've also tried something like:
What am I missing?
I can confirm that by modifying the template, the buttons should be removed. In the viewer's template double-check once again that you are removing the <li> elements of the <ul id="trv-main-menu-ul"> like the following:
I noticed that the second code snippet contains the html of the side menu, not the main menu, as it has <span> elements before the closing </a> and </li> tags. For example:
Please remove the corresponding elements from the main menu and start the application once again with browser cache cleared.