Approved
Last Updated: 23 Jan 2020 09:36 by ADMIN
If you click multiple times fast on the Next button of the viewer while on the penultimate page, an error may occur. The error indicates that a page with a page number that does not exist in the report - 'pageCount+1' is missing. The error message persists even if you navigate to other pages. The issue occurs in SINGLE_PAGE pageMode.
Pending Review
Last Updated: 23 Jan 2020 04:41 by Carl

Hi

If I run the angular report viewer within my main page, all is well. However if the report viewer is hosted in a <p-dialog> (or <p-overlaypanel>), the report does not render (even though data is loaded and the report can be exported). To confirm this, I even have the report visible in a <tr-viewer> on the main page behind the dialog and load them at the same time.

If the dialog is not visible when the main page opens, then the report viewer toolbar is in a column on the left, and is not operational. (see attached)

If the dialog is visible when the main page opens, then the toolbar appears at the top and functions normally. (see attached)

 

<tr-viewer #rptViewerBody
     [containerStyle]="viewerContainerStyle"
     [serviceUrl]="reportServerUrl"
     [viewMode]="'INTERACTIVE'"
     [scaleMode]="'SPECIFIC'"
     [scale]="1.0">
</tr-viewer>

vs

<p-dialog modal="true"
          appendTo="body" 
          header="Report"
          [(visible)]="showReport"
          [width]="1500" 
          [height]="1500">

        <tr-viewer #rptViewerDialog
            [containerStyle]="viewerContainerStyle"
            [serviceUrl]="reportServerUrl"
            [viewMode]="'INTERACTIVE'"
            [scaleMode]="'SPECIFIC'"
            [scale]="1.0">
        </tr-viewer>
</p-dialog>

 

In the code, I tried both of these container styles. The result for the dialog was that relative position rendered the toolbar (top or left), but absolute position rendered nothing at all (height became 0)

this.viewerContainerStyle = {
      position: 'absolute',
      top: '0px',
      left: '0px',
      right: '0px',
      bottom: '0px',
      ['font-family']: 'ms sans serif'
    };
this.viewerContainerStyle = {
      position: 'relative',
      width: '1300px',
      height: '1300px',
      ['font-family']: 'ms sans serif'
};

 

using @progress/telerik-angular-report-viewer": "7.19.718"

 

Thanks.

Declined
Last Updated: 22 Jan 2020 09:30 by ADMIN
Sometimes when the width of the page is less than the one of the report (<13px). This content on the right side (the last 12px) will be not visible.
Completed
Last Updated: 22 Jan 2020 09:30 by ADMIN
Release 2020\R1
Created by: Nasi
Comments: 0
Type: Bug Report
1

In HTML5 Report Viewer it is possible to intercept a client request (e.g. the request to export a report to a particular export format) and modify it like this:

{"format":"<script>alert(1)</script>","deviceInfo":{"enableAccessibility":false,"enableSearch":true,"BasePath":"/COAT_SIT/api/reports"},"useCache":true,"baseDocumentID":"31d0a1ca0162a3f13e92bf"}

The malicious script will be executed when the error message for a missing export format is displayed in the viewer.

In Development
Last Updated: 22 Jan 2020 09:28 by ADMIN
Scheduled for 2020\R1 SP1
The TOC is missing when the report is exported programmatically to Word in .NET Core application
In Development
Last Updated: 22 Jan 2020 09:27 by ADMIN
Scheduled for 2020\R1 SP1
When providing both inline JSON and service Url to WebServiceDataSource, in design time the data is requested from the service instead of being taken from the inline JSON to reduce the network load.
Approved
Last Updated: 21 Jan 2020 11:04 by ADMIN
Created by: Ludek
Comments: 1
Type: Bug Report
1

Print functionality doesn't work in React application.

Steps to reproduce:

1. You may use the sample project from How to use HTML5 Report Viewer in React Application article.

2. Run the project and click on Print.

The following error can be seen in the browser's console: Resource interpreted as Document but transferred with MIME type application/pdf: "https://demos.telerik.com/reporting/api/reports/clients/a7fdd020ec4/instances/3f53abd1614/documents/c3923e685e6d6ebefb3d11?response-content-disposition=inline".

Approved
Last Updated: 21 Jan 2020 10:30 by ADMIN
If the report contains an HtmlTextBox with no content or whitespace as content, the generated PPTX document is corrupted.
Completed
Last Updated: 16 Jan 2020 11:54 by ADMIN

When the user confirms changing the chart type through the "Change Chart Type" dialog window, the graph designer does not get refreshed and still shows the old chart type.

Underneath the graph item is actually changed and if the report is previewed, the new graph layout will be displayed. The current workaround is to refresh the graph designer by changing one of its properties that cause full item refresh - Culture, Graph title, NoDataMessage, etc.

Approved
Last Updated: 10 Jan 2020 15:56 by ADMIN

Under Linux, when the font is set with Conditional Formatting some of the TextBoxes may be rendered with different that the expected Font in Docx. Other TextBoxes set with the same rule to the same font are rendered correctly.

The same report rendered in Docx under Windows produces the correct document.

Approved
Last Updated: 06 Jan 2020 10:07 by ADMIN
Created by: Paul Johnson
Comments: 0
Type: Bug Report
1
If you export a table in RTF whose content is longer than 1 page, in the exported document the whole table will be placed on one page only and the rows that are in the end might not be seen.
Pending Review
Last Updated: 20 Dec 2019 12:44 by Hans

When the culture of the thread is the default one, the private font (e.g. "Shadow Brush") will be replaced with a substitute in the Html5 Viewer (e.g. "Verdana") as the viewer does not respect private fonts. This is normal and expected behavior. When exported to PDF the text is displayed with the correct font ("Shadow Brush") but the embedded font as claimed by the Font properties of the PDF document reader is the substitute font ("Verdana").

When the culture of the thread is changed, the private fonts are not respected and not embedded in PDF rendered document at all. The text does not appear.

Completed
Last Updated: 13 Dec 2019 15:27 by ADMIN
When you choose the option to print the report you get the print dialog. You select page 1 and print. After that you get a dialog saying "Printing ..." and after that, it is closed but the page is never shown on the printer. I tested this on several printers, including virtual, and page never reaches any of them. If you print the entire document, the first page is printed successfully with the rest of the report.
Completed
Last Updated: 13 Dec 2019 15:20 by ADMIN
When exporting a report to PDF on Linux the document looks correct. If you try to copy text from this PDF and paste it in a text editor, the text appears as random symbols, e.g. empty squares.
Completed
Last Updated: 13 Dec 2019 15:20 by ADMIN

As virtually every product with 10+ years of development, Telerik Reporting has a certain amount of legacy code that was considered immutable at the time of writing. During the refactoring of our codebase to make it compatible with .NET Standard, we introduced a few types from System.Windows.Forms namespace to substitute the ones missing in the current version of the framework. Such types are System.Windows.Forms.CheckState and System.Windows.Forms.ControlPaint. Some of these types are introduced in recent release of .NET Core 3 for Windows Forms and therefore a conflict occurs between the types in our assemblies and the ones declared in .NET Core. The error is thrown in compile-time and it is similar to the one shown below:

The type 'CheckState' exists in both 'System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' and 'Telerik.Reporting, Version=13.2.19.918, Culture=neutral, PublicKeyToken=a9d7983dfcc261be'

 

In a future release of our product this collision will be avoided by using a dedicated enumeration for the duplicated types. A possible workaround would be to add an extern alias to the assembly reference of Telerik.Reporting. In this case all the references to Telerik.Reporting have to be edited to use the new alias, but the code that refers to the actual types from System.Windows.Forms will remain unchanged.

 

Here is how the Telerik.Reporting reference would look like in the application .csproj file:

  <ItemGroup>
    <Reference Include="Telerik.Reporting">
      <HintPath>..\..\..\Bin\netstandard2.0\Telerik.Reporting.dll</HintPath>
      <Aliases>telerikReporting</Aliases>
      </Reference>
  </ItemGroup>

 

Using the alias means that all the types in Telerik.Reporting namespace must be accessed with this alias. Unfortunately this also applies to C#/VB report definitions - their types must also be prepended with the alias, which could require significant effort. Here is a sample code file that initializes the WinForms Report Viewer and examines the CheckState of a CheckBox control in the form:

extern alias telerikReporting;

using System;
using System.Windows.Forms;

namespace WindowsFormsCoreDemo
{
    public partial class MainForm : Form
    {
        public MainForm()
        {
            InitializeComponent();
            this.Load += this.Form1_Load;
        }

        private void Form1_Load(object sender, EventArgs e)
        {
            this.reportViewer.ReportSource = new telerikReporting::Telerik.Reporting.UriReportSource()
            {
                Uri = "SampleReport.trdp"
            };

            this.reportViewer.RefreshReport();
        }

        private void CheckBox_CheckedChanged(object sender, System.EventArgs e)
        {
            if (this.checkBox.CheckState == CheckState.Checked)
            {
                this.reportViewer.RefreshReport();
            }
        }
    }
}
Completed
Last Updated: 13 Dec 2019 15:20 by ADMIN
Release 2020\R1
Changing the Telerik Report Viewer pageMode setting through PageMode method does not work correctly
Approved
Last Updated: 09 Dec 2019 17:55 by ADMIN
The report is not exported correctly in PDF when the Font is Sakkal Majalla and Text Align is Right. If you set the Text Align to left, everything works as expected.
Approved
Last Updated: 05 Dec 2019 15:22 by ADMIN

When merging the ReportViewer's WPF theme dictionaries from the DLL in App.xaml, the VS2019 Designer fails due to a problem with a ZoomComboBoxStyle definition.

This causes all Telerik UI for WPF control's styles fail to load in the Visual Studio designer.

WORKAROUND

Instead of App.xaml, merge the ReportViewer's theme dictionary closer to the control.

For example in the ReportViewer's direct parent:

<Grid>
<Grid.Resources>
<ResourceDictionary>
<ResourceDictionary.MergedDictionaries>
<!-- Moved from app.xaml -->
<ResourceDictionary Source="/Telerik.ReportViewer.Wpf.Themes;component/Themes/Summer/Telerik.ReportViewer.Wpf.xaml" />
</ResourceDictionary.MergedDictionaries>
</ResourceDictionary>
</Grid.Resources>

<tr:ReportViewer x:Name="ReportViewer1" ReportSource="{Binding CurrentReport}" />
</Grid>

Approved
Last Updated: 04 Dec 2019 14:00 by Mark

Hello Telerik team!

In the attachment, there are two PDFs, generated by the same template (also in attachment): one built under Windows, another one - under Linux (Docker). See red boxes as defects on the screenshot:

Text wrap issues

Text wrap issues

Dockerfile fragment:

# MS TrueTypeFonts install
RUN wget http://ftp.de.debian.org/debian/pool/contrib/m/msttcorefonts/ttf-mscorefonts-installer_3.6_all.deb -P ~/Downloads
RUN apt install -y ~/Downloads/ttf-mscorefonts-installer_3.6_all.deb

RUN apt-get install -y libc6-dev
RUN apt-get install -y libgdiplus
RUN apt-get install -y libx11-dev
RUN rm -rf /var/lib/apt/lists/*

 

Please help us to resolve these issues in Linux.

Approved
Last Updated: 04 Dec 2019 10:13 by ADMIN

When you try to send the report through the SendMailMessage functionality but an exception is thrown, the report will disappear. If you click on Refresh and try again with fake data, the exception will be thrown but the report will remain. If you prefer to refresh it automatically, you can use the error event:


var viewer = $("#reportViewer1")
.telerik_ReportViewer({
    serviceUrl: "api/reports/",
    reportSource: {
        report: "Report Catalog.trdp",
    },
    error: function (e, args) {
        console.log("This event handler will be called after a page of the report is ready.");
        console.log("The error message is: " + args);
        viewer.refreshReport();
    },
    viewMode: telerikReportViewer.ViewModes.INTERACTIVE,
    scaleMode: telerikReportViewer.ScaleModes.SPECIFIC,
    scale: 1.0,
    enableAccessibility: false,
    sendEmail: { enabled: true }
}).data("telerik_ReportViewer");

1 2 3 4 5 6