I run an ASP.NET Core application that has the functionality to export reports into PDFs in an Azure environment.
There is no way to install additional fonts on Azure so I provide the fonts used in my reports via the "privateFonts" element of the Reporting configuration.
This works for the most part, the font is embedded in the produced PDFs but if I have a textbox with a large text, the text may be cut off when using the Skia engine.
I tested running my application in Docker, I copied the needed fonts in the usr/share/fonts directory of the Docker Linux container, and tried exporting again.
When exporting from Docker, with the fonts installed in the container, the text is not cut off. It seems that there is an issue when the fonts are provided as private fonts.
I use the kendovalidator before rendering the report to check the correct parameter of initial and final date.
However, the validation fails because additional inputs (for the "Send Email" functionality) are included in the HTML output of the viewer even though I have disabled it.
I believe that if the "Send Email" option is disabled the mail data panel should not be created.
If we initialise the control in "FIT_PAGE_WIDTH" mode it essentially renders as expected but zooming in can actually then cause it to zoom *out*.
Reproducible in the `CSharp.NetFramework.Html5IntegrationDemo` example project as well, once you set the `scaleMode` property to "In FIT_PAGE_WIDTH".
In print preview, if you have "FIT_PAGE_WIDTH" as a default scale mode, once you click the "toggle full page/full page width" button, it's never possible to get it to return the original fit-page-width size (it seems to cycle between 3 different zoom modes, but none of them fill the entire control width).
It looks like the report viewer correctly sets the scale mode during initialization. However, when toggling the mode later, it sets it incorrectly.
If I try to drag & drop fields in the Standalone Report Designer for .NET, it does not allow me to paste the field, and the icon changes, indicating that the action is not allowed.
On the other hand, I can drag & drop the fields as expected when using the Standalone Report Designer for .NET Framework.
I have updated to version 19.2.25.813 of Reporting, and when I try to build a project that has Reporting references, I get the following warnings:
Telerik and Kendo UI Licensing warning TKL102: Your current license has expired and is not valid for Telerik Document Processing Libraries version 2025.2.807.20.
There are no Telerik Document Processing dependencies in my project, but I still get the warning.
Currently, the VS item templates, and the documentation suggest using app.UseEndpoints for route registration in ASP.NET Core.
It would be better to use top-level route registrations like app.MapControllers() and app.MapControllerRoute() directly.
Currently, the desktop viewers don't allow adding custom headers to their requests to the service.
In HTML5-based web viewers, this is possible through the AjaxPrefilter event.
My use case is a multi-select parameter that is based on a dataset; and the dataset is filtered by 2 other parameters.
The dependent parameter editor is shown as a SpinButton rather than a multi-select editor in the Blazor Native Report Viewer:
When exporting a report to Excel with the UseExtendedFormatting parameter set to False, the Standard DateTime Format Strings are hard coded as custom formats in the generated XLS/XLSX document.
The custom formats correspond to the current regional settings or, if the report is rendered with a specific culture, the default date format strings for the selected culture.
While customising templates/CSS, I noticed the .trv-parameters-wrapper div as follows:
<div tabindex="300" class="trv-parameters-wrapper" aria-label="Parameters area. Contains 4 parameters.">
<div class="trv-parameter-container k-card"></div>
</div>
Hi Team,
Currently, the DatabaseCacheConfigurator.exe tool seems to be Windows-only. Can you please compile this to be cross platform compatible? I am on macOS and cannot use any Windows tooling.
Thank you,
Frank
We use WPF Report Viewer in our application. For testing, validation, and automation purposes, we need to:
If I set the ReportSource to the Native Blazor Report Viewer using @bind directive, for example:
@bind-ReportSource="@ReportSource"
ReportSource="@(new ReportSourceOptions { ... })"
It causes the viewer to go into a loop of trying to set the ReportSource, and it never renders the report.
Hi Team,
I have a request for being able to add the `User-Agent` header to reporting calls. We've ran into some image hosting sites that will not resolve image links properly if the user-agent is not present in the request and returns a 403 Forbidden error. Any browser that passes the user-agent parameter can resolve this link.
https://cms5.revize.com/revize/cityofwillmar/_assets_/images/logo.png
But telerik will return this error:
Telerik.ReportDesigner.exe Error: 0 : An exception has occurred while processing 'pictureBox1' item: System.Net.WebException: The remote server returned an error: (403) Forbidden. at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request) at System.Net.WebClient.DownloadData(Uri address) at Telerik.Reporting.Processing.Imaging.ImageUtils.LoadData(String filePath) at Telerik.Reporting.Processing.Imaging.UrlImageItem.CreateUnderlyingImageItem() at Telerik.Reporting.Processing.Imaging.UrlImageItem.get_UnderlyingImageItem() at Telerik.Reporting.Processing.Imaging.UrlImageItem.CreateImageInfo() at Telerik.Reporting.Processing.Imaging.IImageInfoMapExtensions.StoreImageData(IImageInfoMap imageInfoMap, IImageItem imageItem, ICache cache) at Telerik.Reporting.Processing.PictureBox.ResolveImage(Object value) at Telerik.Reporting.Processing.ReportItemBase.ProcessElement() at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)
Currently, the only way around this is to fetch the images with a custom user function and returns the images to the Reporting Engine as a byte array or other supported format. It's a lot of overhead for something that could simply be toggled on an off, so I think this would be a nice feature addition.
Thanks,
J.T.
If I set both the "EnableAccessibility" and "ViewerRenderToolTips" device info settings to true, the generated PDF document is corrupted.