Telerik Reporting R2 2018 SP1: What's New and Improved
Telerik Reporting is a powerful reporting solution that enables you to create, view, and export rich, interactive, and reusable reports. It supports various data sources, report formats, and rendering options.
In this article, we will review some of the new and improved features that are available in Telerik Reporting R2 2018 SP1 (version 126.96.36.1990) Retail[^1^].
The currently exported format name is now available in the expression context. This allows you to customize the report content based on the output format.
You can now change the PDF documents Creator and Producer meta information using the PdfDocumentOptions class.
The Conditional Formatting editor has been improved to support multiple items selection and editing.
You can now add additional user data to the UserIdentity object using the UserData property. This can be useful for passing custom information to the report engine or data source components.
The HTML5 report viewer template is now localizable using JSON files. You can easily translate the viewer UI to different languages or cultures.
The desktop viewers now support bitmap image formats for Azure deployment. This enables you to use images stored in Azure Blob Storage as report resources.
The WPF SearchDialog Window now supports the WPF themes. You can apply different themes to the search dialog using the StyleManager class.
The WPF Report Viewer XAML dependencies are now part of Telerik.ReportViewer.Wpf.Themes assembly. This simplifies the process of upgrading or changing the viewer theme.
An error occurs when adding new child group to a row header group of CrossTab if there are merged cells in adjacent group.
Can't add new parameter in Web Service Data Source Wizard after error.
Telerik.Reporting.OpenXmlRendering assemblies are not listed in Visual Studio Assemblies tab.
Upgrade Wizard is not upgrading the web page containing the HTML5 Report Viewer if it is under source control.
Upgrade Wizard leaves more files than expected in the project.
Indented and justified text inside HtmlTextBox is not layout correctly.
Non-informative exception is thrown when the Graph item fails to resolve its data.
PictureBox value defined as a relative path in declarative report definition is not resolved correctly.
Processing never finishes when report parameter's AvailableValues.Filters use nonexistent report parameter.
A GDI error occurs when rendering report with image on Azure (Excel and PowerPoint formats).
PageSettings.Landscape property is not respected for reports with shorter width (Word format).
When PageSetting.ContinuousPaper is True the paper size is not respected (Word format).
CreateJsonResponse utility method is treated as an action method by the framework (WebAPI ASP.NET Core).
All dynamic class names should start with trv- (HTML5 Report Viewer).
FullPage/PageWidth button state is not visually toggled when in PageWidth state (HTML5 Report Viewer).
Invocation of isExceptionOfType function should happen via utils object (HTML5 Report Viewer).
PictureBox value defined as a relative path in cs/vb report definition is not resolved correctly in Web apps (HTML5 Report Viewer).
Table of contents is overlapped by vertical and horizontal scrollbars on hover (HTML5 Report Viewer).
Toolbar buttons selected state is missing (HTML5 Report Viewer).
Missing tooltip \"Stop Search\" over the X button of report content search area (Windows Forms Report Viewer).
Multipage reports display only the first page after Resizing/Restoring Window (Windows Forms Report Viewer).
Selecting an item in SearchDialog always scrolls the report area (Windows Forms Report Viewer).
Search dialog is shown as TopMost form instead of TopLevel for its parent form (Windows Forms Report Viewer).
Non-informative exception is thrown when the search dialog is opened aa16f39245