The RTF rendering automatically switches to the Tables rendering mode whenever a Crosstab/Table/List is detected in a report. This rendering mode throws an exception whenever the report contains PictureBox with one of the following sizing options.

• Center
• Normal
• Stretch
• ScaleProportional

The RTF export should work with all PictureBox sizing options regardless of the rendering mode.

To work around the issue currently, one can either force the rendering engine to use the Frames rendering mode using the RenderingMode device information property or set the Sizing property of all picture boxes in the report to AutoSize.

When a report contains multiple DateTime parameters, the viewer assigns the first value to all of them regardless of their default values or the values passed in the viewer's report source.

Additionally, if one clicks the preview button quickly after changing the value of a DateTime parameter, the old value is passed to the service even though the parameter editor is updated. To avoid this, the user needs to wait a second before previewing.

When testing integer values outside the range of System.Int32 (-2147483648 to 2147483647) for a multi-value integer parameter, I started to get the error:

An error has occurred while processing Report '___':
Cannot perform '=' operation on System.Int32 and System.Int64.

I narrowed this down to the "In" and "Between" operators. For example, the expression evaluating a literal integer value against the multi-value parameter:

= 0 In Parameters.IntegerMultiVal.Value

It appears that the literal integer is being converted, internally, to Int32 and compared against the contents of the multi-value parameter as Int64 - though the error only occurs when a value outside the Int32 range is present.

= Parameters.IntegerSingleVal.Value = 0

= Parameters.ZeroVal.Value In Parameters.IntegerMultiVal.Value

This was tested and reproduced in the HTML5 report viewer and the standalone report editor.

The HTML5-based report viewers use the following navigation icons.

• Arrow with a line to navigate to the next/previous page.
• Double arrows to navigate to the first/last page.
  

This is unintuitive and inconsistent with the desktop and native report viewers.
The navigation icons should instead be:

• Single arrow to navigate to the next/previous page.
• Arrow with a line to navigate to the first/last page.
  

Adding the "Telerik.ReportViewer.WinUI.Themes/Themes/Generic.xaml" theme to a WinUI project causes existing AppBarButtons to grow in size because it overrides the AppBarButtonContentHeight setting.

The report viewer theme should not override the styles of the default WinUI controls.

If you set the WinUI viewer's ViewMode to PrintPreivew in the XAML or the code, the toolbar button's state and value don't change. Hence, even though the report is displayed in PrintPreview, the button for switching the ViewMode is still showing 'Switch to PrintPreview' and is not highlighted. When you click it, the report is displayed in Interactive View, the button becomes highlighted and the tooltip states 'Switch to Interactive mode'.

If cells grow or shrink, if there are hidden cells, any time a report section grows vertically, the next section/table is not respecting the growing of the previous item and text prints in the wrong spot or the table overlaps the previous table.

A potential workaround is to manually convert the troublesome tables to lists where possible.

I have denied the permission to use the Asset Manager in the configuration of the service of the Web Report Designer. This is generally respected and I do not see the option to open the asset manager from the main menu but when I try to set an image to a PictureBox item, I still see the option to add it from the assets and the button is also clickable.

With that being said, the permission is respected on the server and I get an error about not having permission to use the Asset Manager when I click on the button. Still, it will be better if the button is removed from the UI altogether when I have disabled the assets.

Password-protected PDF documents generated with Telerik Reporting have blank pages when opened with an iPhone.

When I deploy the Angular HTML5 Report Viewer demo on Docker and build for production I receive the next error:

main.fa32b7794d384513.js:1 Uncaught Error: Invalid template:'<td class="#=data.cssClass#" role="gridcell"><a tabindex="-1" class="k-link" href="\#" data-#=data.ns#value="#=data.dateString#">#=data.value#</a></td>' Generated code:'var $kendoOutput, $kendoHtmlEncode = kendo.htmlEncode;$kendoOutput='<td class="'+(data.cssClass)+'" role="gridcell"><a tabindex="-1" class="k-link" href="#" data-'+(data.ns)+'value="'+(data.dateString)+'">'+(data.value)+'</a></td>';return $kendoOutput;'
    at Object.compile (main.fa32b7794d384513.js:1:269410)
    at main.fa32b7794d384513.js:1:565164
    at Object.dt (main.fa32b7794d384513.js:1:598166)
    at 961 (main.fa32b7794d384513.js:1:1411020)
    at n (runtime.142728358b17fb3f.js:1:128)
    at 735 (main.fa32b7794d384513.js:1:117899)
    at n (runtime.142728358b17fb3f.js:1:128)
    at 158 (main.fa32b7794d384513.js:1:110372)
    at n (runtime.142728358b17fb3f.js:1:128)
    at main.fa32b7794d384513.js:1:1503100

When I remove the viewer from the project the problem disappears.

With the same 'Dockerfile' and 'nginx.conf' the Native Angular Report Viewer works as expected.

To preview/export localized reports in different languages, I change the thread's current culture in the report viewer's ExportBegin/RenderingBegin events and reset it back to the original culture in the ExportEnd/RenderingEnd events.

This approach works well in .NET Framework projects but in .NET Core projects, the culture is not reset properly.

Changing the culture in the events of the desktop report viewers should work both in .NET Framework and .NET Core projects.

The Upgrade Wizard for Visual Studio backs up all files, including those in the '.vs' folder. In Visual Studio 2017 this may cause errors when upgrading due to the locked file 'db.lock':

System.IO.IOException: The process cannot access the file 'C:\Users\reportingagentuser\Desktop\reportlibrary1\ReportLibrary1\.vs\ReportLibrary1\v15\Server\sqlite3\db.lock' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
   at System.IO.File.Copy(String sourceFileName, String destFileName, Boolean overwrite)
   at Telerik.Reporting.UpgradeWizard.Engine.Services.BackupService.BackupDirectory(String directoryName)
   at Telerik.Reporting.UpgradeWizard.Engine.Services.BackupService.BackupDirectory(String directoryName)
   at Telerik.Reporting.UpgradeWizard.Engine.Services.BackupService.BackupDirectory(String directoryName)
   at Telerik.Reporting.UpgradeWizard.Engine.Services.BackupService.BackupDirectory(String directoryName)
   at Telerik.Reporting.UpgradeWizard.Engine.Services.BackupService.BackupDirectory(String directoryName)
   at Telerik.Reporting.UpgradeWizard.Engine.Services.BackupService.BackupDirectory(String directoryName)
   at Telerik.Reporting.UpgradeWizard.Engine.ProjectItem.BackupInternal()
   at Telerik.Reporting.UpgradeWizard.Engine.UpgradeItem.Backup()</event>

The Preview button of the HTML5 Report Viewer is not styled appropriately when using Kendo SASS themes:

.NET applications do not support rendering extensions like the XPS and MHTML rendering but the Reporting engine attempts to resolve them in such applications regardless.

There should be no attempts to resolve unsupported rendering extensions in .NET applications.

Dear Telerik 

Please see thread on Report does not bring byte[] image through to PictureBox when rendered programmatically. | View Ticket | Your Account (telerik.com)

KR

David

I use HTML content like the below in an HtmlTextBox:

<a style="color: red" href="some link here">some text</a>

The color is not respected when I export to PPTX. The output color of the generated link is always the default blue. In the rest of the formats that support hyperlinks, the color is correct.

I tried to wrap the <a> tag also with <p> and <span> with the same color setting, to no avail.