Completed
Last Updated: 30 Jul 2020 09:43 by ADMIN

When Windows display scaling is set to 150%, the stand-alone report designer causes the resulting Excel Worksheet export to shrink from its expected layout.

Steps to reproduce:

  1. Set display scaling to 150% in Windows Display Settings
  2. Start the standalone Telerik Report Designer and open the Invoice example report
  3. Preview the report for order SO51081 and export to "Excel Worksheet"
  4. Open the report in Excel.
    Issue:
    Its formatting is not as expected, note the contact name is cut off and overall the output is squished together.
  5. Close the Telerik Report Designer
  6. Set display scaling to 100% in Windows Display Settings
  7. Repeat steps 2 through 4 and note the improved rendering of the Excel Worksheet at standard display DPI.

I've attached my XLSX file results for 150% scaling and 100% scaling to show the problem.

I would not expect my display settings to alter the export of Excel Worksheet files in the Telerik Report Designer application.

150%:

100%:


Completed
Last Updated: 24 Jul 2020 16:35 by Bernard
Release 2020 R2 (Latest Internal Build)

Standalone Report Designer is not localized when the trdp file is opened. The localization only takes effect when the executable file is started first and then the report is opened. 

Reproducible in R2 2020 14.1.20.513

Completed
Last Updated: 23 Jul 2020 15:41 by Tony
Release 2020 R2
It would be good if the table headers can be frozen.  This can  be really useful in case of a big report which is displayed on a single page.
Completed
Last Updated: 14 Jul 2020 19:09 by Thomas

If during the report rendering stage, one or more of the required entities in the File storage were removed/deleted by third-party software, it will prevent the report from finishing the rendering and throws a NullRefereceException:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Reporting.Services.Engine.Document.AddClientToolTipsResource(IList toolTips)
   at Telerik.Reporting.Services.Engine.Document.FinishRendering(ReportRendererResult result)
   at Telerik.Reporting.Services.Engine.ReportEngine.RenderReportDocument(String pendingRenderingId)
   at Telerik.Reporting.Services.Engine.TaskQueue.WorkerThread.ProcessItems()
   at Telerik.Reporting.Services.Engine.TaskQueue.WorkerThread.ThreadProc()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()]

Completed
Last Updated: 07 Jul 2020 10:06 by ADMIN
Release 2020 R2
In some cases, the error "Child doesn't implement ITableCell" can be thrown when the EnableAccessibility property of the viewer is set to true. To avoid it, set EnableAccessibility to False.
Completed
Last Updated: 18 Jun 2020 12:43 by ADMIN
Release R2 2020 SP1
Due to breaking API changes in .NET Core 3.0, the .NET Standard 2.0 build of the Telerik.WebReportDesigner.Service is not compatible with .NET Core 3.0. The package should provide a variant of the assembly targeting .NET Core 3.0.
Completed
Last Updated: 18 Jun 2020 12:43 by ADMIN
Release R2 2020 SP1
Created by: Ludek
Comments: 1
Type: Bug Report
3

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".

Completed
Last Updated: 18 Jun 2020 12:42 by ADMIN
Release R2 2020 SP1
When the DataMatrix encoder is used in Barcode item and the provided value evaluates to null or an empty string, the barcode item renders an exception message rather than rendering an empty placeholder.
Completed
Last Updated: 18 Jun 2020 12:42 by ADMIN
Release R2 2020 SP1
When I set all Graph Paddings to 0 and LabelPlacement to None, there is still a place left between the Graph Axis and the Graph Border.
Completed
Last Updated: 09 Jun 2020 15:16 by ADMIN
Release 2020 R2 (Latest Internal Build)
The column widths are narrower than their designed size when exporting to XLSX on machines with DPI > 96. In such scenario the cell contents get wrapped, making the report harder to read.
Completed
Last Updated: 08 Jun 2020 08:10 by ADMIN
Release 2020 R2 (Latest Internal Build)
When the WPF ReportViewer is hosted in a RadTabItem, removing the RadTabItem from its RadTabControl doesn't free the memory, occupied by the report viewer instance, thus producing a memory leak.
Completed
Last Updated: 03 Jun 2020 14:11 by ADMIN
Release 2020 R2 (Latest Internal Build)
If the report contains an HtmlTextBox with no content or whitespace as content, the generated PPTX document is corrupted.
Completed
Last Updated: 19 May 2020 13:46 by ADMIN
Release 2020 R2

When exporting to Excel Worksheet, the CheckBox item is rendered as Excel Picture. If the machine settings are higher than the default 96 DPI (100%), the checkbox image is generated with incorrect size and the produced Excel file is corrupted.

Completed
Last Updated: 18 May 2020 17:57 by ADMIN
Release 2020 R2

Steps to reproduce:

1. Create a Blazor application;

2. Add Teleri.Reporting NuGet package;

3. Add Telerik.WebReportDesigner.Services Nuget package -> some of the app dependencies are broken.

 

Solution:

Refer the .NET Standard DLLs from C:\Program Files (x86)\Progress\Telerik Reporting <Version>\Bin\netstandard2.0.

Completed
Last Updated: 14 May 2020 07:02 by ADMIN
Release 2020 R2
Created by: Kevin
Comments: 21
Type: Feature Request
35
Please add support for Data Matrix barcodes.  As of Q3 2014 this is the only format we will still need to rely on another library to create an image that is placed in a picture box.  We would much rather be able to use the Barcode control for all our barcode requirements.
Completed
Last Updated: 13 May 2020 13:11 by ADMIN
Release 2020\R2
When parameterized WebServiceDataSource is used for the AvailableValues of Report Parameter, the change of the WebServiceDataSource parameter value doesn't trigger a refresh in the AvailableValues.
Completed
Last Updated: 13 May 2020 13:07 by ADMIN
Release 2020 R2
Created by: Karim
Comments: 3
Type: Feature Request
7

It would be very handy, if the value property of the PictureBox would resolve images from base64 strings besides the Image, Image byte[], relative or absolute URI.
It should be fairly simple to implement. I wrote my own user function for this. It would be beneficial to have this out of the box.


[Function(Category = "Image", Namespace = "ImageFunctions", Description = "Converts a base64 string to an image byte array")]
public static byte[] ConvertFromBase64(string imageString)
{
    if (imageString != null)
    {
        // Convert base 64 string to byte[]
        byte[] imageBytes = Convert.FromBase64String(imageString);
        return imageBytes;
    }
    else
    {
        return null;
    }
}

Completed
Last Updated: 13 May 2020 12:49 by ADMIN
Release 2020 R2

When the SqlDataSource wizard uses a connection to a non-MSSQL database, which is registered in a Report Server instance, previewing the results on the "Preview data source results" page will throw an exception.

Completed
Last Updated: 13 May 2020 12:49 by ADMIN
Release 2020 R2
The Map item cannot determine correctly the appropriate zoom level when the map extent is set to a relatively small area - less than 0.1 degrees latitude/longitude.
Completed
Last Updated: 13 May 2020 12:49 by ADMIN
Release 2020 R2
We are hosting our ASP.NET Core Application in a Linux Container on Azure. When we export the report in Linux there are additional spaces at the end of each paragraph. However, when we export the report on Windows the carriage return appears fine. 
1 2 3 4 5 6