Completed
Last Updated: 02 Apr 2020 10:27 by ADMIN
Release R1 2020 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.
Completed
Last Updated: 27 Mar 2020 15:13 by ADMIN
Release 2020 R1 SP2 (Latest Internal Build)
The GetResource() endpoint of the AspNet.Core REST service always adds the "Cache-Control" header to the response's headers collection. This causes an exception when such header already exists.
Completed
Last Updated: 27 Mar 2020 15:13 by ADMIN
Release 2020 R1 SP2 (Latest Internal Build)
The PDF export produces an invalid document when the accessibility features are enabled and the engine runs in Docker environment with Linux containers.
Completed
Last Updated: 27 Mar 2020 15:13 by ADMIN
Release 2020 R1 SP2 (Latest Internal Build)
Exporting a report with enabled accessibility to PDF or TIFF formats results in ArgumentOutOfRangeException.
Completed
Last Updated: 27 Mar 2020 15:13 by ADMIN
Release 2020 R1 SP2 (Latest Internal Build)

The labels of the axes and data points of a Bar chart are not correctly placed in PDF rendering when using .NET Core. The Graph is rendered on multiple pages. The appearance on the first page is correct and deteriorates on the next pages.

In.NET Framework, the same report is rendered as expected.

Completed
Last Updated: 27 Mar 2020 15:13 by ADMIN
Release 2020 R1 SP2 (Latest Internal Build)

The label connectors are not displayed when the graph contains a second coordinate system, which is configured for non-pie charts, but is not used by the graph series.

Pie chart coordinate system has Category Scale for its Radial Axis and Numerical Scale for its Angular Axis.

Since the second coordinate system is not used by the series it should not affect the appearance of the label connectors.
Completed
Last Updated: 27 Mar 2020 15:13 by ADMIN
Release 2020 R1 SP2 (Latest Internal Build)
The Context Menu does not pop-up when you right-click on a Report Parameter in the Report Explorer of the designer.
Completed
Last Updated: 27 Mar 2020 15:13 by ADMIN
Release 2020 R1 SP2 (Latest Internal Build)
When there are two data items sharing the same CubeDataSource with query with parameters, the first data item is rendered correctly and the second one throws the exception 'An error has occurred while processing Graph 'graph1': Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index.'
Completed
Last Updated: 26 Feb 2020 16:26 by ADMIN
Release R1 2020 SP1
The File cache is not cleaned by the REST Service after stopping it. This can be observed with the default cache settings and a report with a large image, and when the File cache is configured explicitly from the 'cache' element of the Telerik.Reporting configuration section.
Completed
Last Updated: 26 Feb 2020 16:26 by ADMIN
Release R1 2020 SP1
The TOC is missing when the report is exported programmatically to Word in .NET Core application
Completed
Last Updated: 26 Feb 2020 16:26 by ADMIN
Release R1 2020 SP1

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: 26 Feb 2020 16:26 by ADMIN
Release R1 2020 SP1
If the database that is assigned to the report contains empty records, in Linux and Mac the report is rendered on more pages.
Completed
Last Updated: 26 Feb 2020 16:26 by ADMIN
Release R1 2020 SP1
If you add the Telerik.WebReportDesigner.Services package to a working .NET Core 3.1 project using Telerik Reporting, the built fails with System.Reflection.ReflectionTypeLoadException
Completed
Last Updated: 19 Feb 2020 16:23 by ADMIN
On the Print button click, the viewer opens a File Save dialog instead of invoking the Print dialog. Observed with Edge version 79.0.309.71.
Completed
Last Updated: 19 Feb 2020 11:42 by ADMIN

Go to page https://demos.telerik.com/reporting/product-catalog?&skinName=default

Open Search dialog.

Type "Accessories" in search field. Wait for results.

Pick last result (Accessories - page 2) from results list. (page 2 will be opened - correct)

Close search dialog and open it again (or just clear search field).

Type "Accessories" in search field again. Wait for results.

Pick last result (Accessories - page 2) from results list again.

Incorrect behavior: page 1 will be opened instead of page 2; and first result item will be highlighted as selected instead of last result item.

Also I met situation when long results list was scrolled up to top but it was unclear how to reproduce it stable.

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.

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.

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();
            }
        }
    }
}
1 2 3