I am using the ObjectDataSource component of the Standalone Report Designer. However, I get errors mentioning that types from `System.Private.CoreLib` cannot be loaded. This used to work in version 19.3.26.121. The workaround in the latest version is to manually register the `System.Private.CoreLib` assembly in the designer through `assemblyReferences` (File -> Options -> Add).
We are using "@progress/telerik-angular-native-report-viewer": "29.26.211"
Seems options Fit to page/Fit to width are mixed
Fit to page does what Fit to width should be doing and vice versa
In the Report Book’s Edit Parameters dialog, non‑mergeable parameters only show index 0 in the dropdown, even when multiple report instances are present:
Other indexes can be applied only by manually typing the value into the combo box, but this behavior is not intuitive and makes it unclear that parameters can be assigned per instance.
Consider adding support for the `start` attribute of the `ol` element in HtmlTextBox. This would allow us to change the start counting:
in the expression editor i have a html tag like this...
<ol style="list-style-type: lower-roman" start="2">
design view on the expression editor correctly shows the indented list starting with ii (2).
On the main report view and print, it only shows as i (1).
Yet any editing it switches back to ii (2);
---
Comment from admin: The HtmlTextBox item does not (yet) support the `start` attribute (please check Styling and Formatting HtmlTextBox). Therefore, the result in the report preview/print is the expected one, while the design view is misleading.
I have created an ellipse shape item and have set its Stretch property to True. Then, I have set the width of the item to be 1.5in, while the height is 1in, which results in a horizontally stretched ellipse on design-time:
However, when I render the report on Linux where the Skia graphics engine is used, the shape is not rendered properly:
After updating to the Q1 2026 release of Reporting, I get the following error when passing the value of a DateTime parameter from the main report to a DateTime parameter of a report that I open via the Navigate To Report action:
CSharp.Net10.ReportingRestServiceCorsDemo Error: 0 : Parameter /Date(1771253073461)/ does not match Epoch regex format! CSharp.Net10.ReportingRestServiceCorsDemo Error: 0 : Parameter /Date(1771253073461)/ does not match Epoch regex format!
The issue seems to occur only when directly passing the value of the DateTime report parameter, so as a workaround, I decided to create a new date using the Date() function. For example:
When I invoke a cancellation before the report processing starts, the expected behavior is that the report should really not even begin processing, but it runs to completion.
When I export to XLSX, RTF, and CSV formats, and try to cancel the report a few seconds later, so that cancellation is signaled while report processing is already occurring, it doesn't stop. The expected behavior is that a TaskCanceledException should be raised, and the report processing should stop, but the report runs to completion. In PDF, DOCX, and PPTX, this works as expected.
The HTML5-based report viewers send 404 request to `/sass/fonts/kendo-font-icons.ttf` when font icons are being used:
Description
Even though there is no map wizard for the WRD, it is possible to create a map item and try to set it. However, it is not possible to select an ESRI Shapefile for the spatial data or inspect the already existing one in the report:
Steps To Reproduce
- Use the PopulationDensity report
- Open the ShapeMapSeries:
- The Source type can't be configured:
Expected behavior
Even with no map wizard in the WRD, the map item should be created from scratch, and all properties should be editable.
Actual behavior
The Source Type doesn't show any option for selecting shape files.
The attached report generates different PDF documents when rendered by the Standalone Designer and REST Service, both targeting the .NET Framework 4.6.2:
- The PDFs have different sizes
- When using the 'Read out loud' functionality of the Adobe Reader, the items are read in a different order. The order in the PDF generated by the designer is correct, and the one in the service-generated PDF is wrong.
My report has a Text Watermark as part of the PageSettings, and is configured for Accessibility. The report contains a Page Header and Page Footer. In the Page Footer, there are two TextBoxes.
When I generate an accessible PDF with Telerik Reporting and use the Adobe Reader > Read Out Loud functionality, it doesn't read the content of the second TextBox in the Page Footer.
Some of the Web Report Designer pop-up messages are not localizable. For example, the message about trying to access a report that does not exist on the server:
Related to:
Also affects Telerik.Reporting.Processing and Configuration: Attempt by security transparent method 'Telerik.Reporting.Processing.AssemblyRefManager.LoadAssembliesCore()' to access security critical method 'Telerik.Reporting.Configuration.ReportingConfiguration.get_Current()' failed.
Currently, the GetDesignerResource endpoint of the Web Report Designer service is case-insensitive, which can lead to issues if the URL is made lowercase at some point, such as by a URL rewrite rule, or similar scenarios.
For example, the following reference to the Web Report Designer script will load return the file:
<script src="api/reportdesigner/designerresources/js/webReportDesigner"></script>But if lowercase is used, for example, like this:
<script src="api/reportdesigner/designerresources/js/webreportdesigner"></script>The request will return a 404(Not Found) response.
Using Blazor native reporting component. Our underlying email sending service requires that Subject is not blank, however the UI does not validate the Subject field.
Need to be able to validate that Subject is not blank when user attempts to submit email form.
We are experiencing issues with Telerik Reporting related to RTL text (culture 'ar-JO') rendering, as outlined below:
- Text wrapping is not working correctly within the HTML5 Report Viewer. The text seems to overflow the TextBox.
- When exporting to PDF, the text exceeds its boundaries, does not wrap as expected, and in some cases is cut off.
This also triggers multiple requests without an instance ID and document ID, resulting in 404 Not Found responses.
Please note the spelling error in the k-notificaiton-error class name. Should be k-notification-error:
<div class="trv-parameter-error k-notification k-notificaiton-error" style="">
<span class="k-notification-status k-icon k-i-x-outline"></span>
<span class="trv-parameter-error-message k-notification-content">Parameter value cannot be empty.</span>
</div>
Because of this, error messages are rendered with incorrect color (should be red):
