New to Telerik Reporting? Download free 30-day trial

Actions not working on Preview

Environment

Product Progress® Telerik® Reporting
Application Type Web Application
Report Designers Visual Studio/Standalone Report Designer

Description

In this article, we will discuss a couple of scenarios where report items' Actions are not working on previewing the report both in a report viewer and in a report designer.

Solution

  • Actions not working in Visual Studio - HTML Preview.

    In the Report Designer, integrated in Visual Studio, you can find an option for HTML Preview. The browser used by Visual Studio is Internet Explorer 7, where the Reporting engine applies HTML5 standards to produce an HTML document from the report definition. As a result actions may not work and the report's layout may appear differently than in HTML5-compliant browsers.

    You can use a web application with the HTML5 Viewer to preview the result.

  • Actions not working in Print preview of the report.

    The Print preview mode of a report viewer displays the report the way it will look in a physical format like PDF. In such formats, actions like ToggleVisibilityAction are not active.

    You can switch to Interactive preview mode to have actions working. Depending on the media and the selected rendering format, actions may be supported - Design Considerations for Report Rendering.

  • Drillthrough Report Action (NavigateToReportAction) is not working in preview in the HTML5 Viewer.

    Navigation between reports can be disabled if the target report is specified via InstanceReportSource|XmlReportSource ('Object instance'|'XML markup' in the Load Report Dialog) on configuring the NavigateToReportAction. The ReportSource is handled internally by the Reporting REST service's resolver, which is not designed to handle a custom report instance as an action's target report.

    The usage of an InstanceReportSource|XmlReportSource is unnecessary for reports designed by Report Designers without further customization. Using a TypeReportSource or UriReportSource ('Type name' or 'URL or file') will assure the proper processing and rendering of the action. 

    If you need to handle a custom case where a report instance has to be used, specify via string the target report by using a TypeReportsource|UriReportSource. The string will be sent to the service's Report Resolver. Then you can plug a custom resolver to handle the case in code.

  • Drilldown Report Action (TogglevisibilityAction) does not toggle the visibility of all required items/sections.

    On configuring the ToggleVisibilityAction, you can set a list of targets which includes sub groups, items and sections. Beside setting the targets, you need to set the targets' Visible properties depending on if you want them to be shown or hidden initially - How to: Add a Drilldown Action.

In this article
Not finding the help you need? Improve this article