The R2 2023 Standalone Report Designer for .NET cannot be run with the .NET 7 runtime that previously worked(approach - https://docs.telerik.com/reporting/knowledge-base/how-to-load-dot-net-7-assemblies-in-srd-dot-net).
Error: 'Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.'
The report has a single-value nullable parameter with AvailableValues.
When you preview the report in the Standalone Designer, if you checked Null, the value would be respected.
When you preview the report in Html5 Viewer and the parameter value selection is cleared, instead of rendering the report with a Null value, the report is rendered with the last selected value.
Steps to produce in the Html5 Viewer:
Here is a link to a muted video on how the issue may be reproduced.
If the parameter is not Nullable, the Preview button after step 4 stays enabled, and clicking on it produces the same result as with the Nullable parameter.
When designing reports with lots of parameters (which is very common for my usage), I often get error message "Missing or invalid parameter value" or "Syntax error in expression". I find it very time consuming and annoying to manually check "all" parameters in order to identify which one is causing the issue.
Would it be possible to include more details in these error messages, e.g. by including the name of the (first) incorrect parameter? Preferably for the message in report viewer / preview, but at least in the log file.
https://www.telerik.com/forums/missing-or-invalid-parameter-value-please-input-valid-data-for-all-parameters
Reproducible in 17.1.23.606 - SRD and WRD.
Not reproducible with demo report Product Catalog.
Steps to reproduce the behavior:
Expected behavior
Textbox is shown.
Actual behavior
System.NullReferenceException: Object reference not set to an instance of an object.
at Telerik.Reporting.Processing.DocumentMap.DetermineNodeVisibilityRecursive(BookmarkNode node)
at Telerik.Reporting.Processing.TocSection.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.StackLayout.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.Group.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.StackLayout.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.Report.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.LayoutElement.Measure(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureElement(LayoutElement elementToMeasure, SizeLU availableSize, IMeasureContext context)
at Telerik.Reporting.ImageRendering.ImageReportInteractive.MeasureRootCore(LayoutElement root, PageSettings pageSettings)
at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)
at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(Report report, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback)
at Telerik.Reporting.Processing.ReportProcessor.RenderCore(ExtensionInfo extensionInfo, IList`1 processingReports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
at Telerik.ReportViewer.Common.ReportRenderer.Render(ReportRendererArgs args)
To have a better performance would be nice to cancel report rendering automatically or manually. If I am asking for a big report and after I change parameters and request new report, the previous request is still in progress and it is not going to be cancelled. Therefore I see high memory consumption on continuously refreshing a reports with a big data and after some time I see complete slow down of the Reporting Service and of course slow down of the server itself. The memory in this case is not released and Reporting Service crashes sometimes.
When Kendo version 2023.1.314 is used, the tooltips of the HTML5 Report Viewer and its wrappers flicker when the cursor hovers above them.
Telerik Reporting Version: 17.0.23.315
Currently the generated accessible PDF documents contain tagged elements, but lack information about the logical structure of the PDF document. This prevents screen readers of correctly reading the PDF document contents. The tools like PAC (PDF Accessibility Checker) do not display correctly the document structure.
Hi Team,
Currently, the Angular Report View doesn't appear to support the Ivy rendering. As of Angular 16 (released 4 days ago), the legacy rendering mode is fully removed. Which means the ReportViewer will no longer work in ng16 or later.
So this feature request is to move the ReportViewer to support Ivy (which will support Angular v9 to v16 and later).
Thank you,
Maks
We have many reports that contain grids using Table controls. We are using the HTML Report Viewer with the enableAccessibility option set to “true” to display these reports to application users.
Using this configuration, the report when run in a browser generates markup using absolutely positioned DIVs instead of TABLE tags for the grids in the report. The accessibility company provided documentation that the generated report content is in violation of WCAG 2.1 A, 4.1.2, Name Value Role since the generated report content is neither a semantic HTML table nor adheres to the ARIA table pattern.
Since Reporting Tables are rendered as DIV elements, you need to ensure they implement the following ARIA Design Pattern specifications:
When exporting a graph that has multiple line series and a category scale to CSV, the error "object reference not set to an instance of an object" is thrown.
More specifically, the issue occurs when one or more of the series do not have a corresponding non-null value for every category.
Hello Support-Team,
in the WebReportDesigner, the Edit-Window shows "undefined" for the FieldNames, when selected a second Time.
This is also reproduceable in the demo application: https://demos.telerik.com/reporting/designer.
(see Screenshot in attached Files)
Steps to repoduce:
1. Open the Edit-Window for a TextBox (with a DataSource)
2. Select the DataSource-Entry.
3. Select some other Entry, e.g. "Report Parameters"
4. Select the DataSource-Entry.
Best regards
Alexander Schneider
System Development | Loy & Hutz Solutions GmbH
Currently, the ReportDesignerControllerBase class does not enforce its own JsonSerializerSettings, rather it uses the ones set globally, on the application level. This could potentially lead to errors since the Web Report Designer requires the data to be serialized in camelCase. When PascalCase is used, certain functionalities get broken.
A way to avoid this would be to explicitly define JsonSerializerSetting in the ReportDesignerControllerBase class so that the Report Designer service does not break regardless of the setting defined on the application level.
As a developer I would like to have a built-in support for rendering various gauges in the report content So that I can represent numeric values in a visually appealing way.
This is not a clone. It's a new request I had to add, since the old was closed with a technically fault answer. By technically fault I mean possible, but in real scenario unusuable. F.e Jasper's SubReports have a property called DataSource. The sub-reporst uses this dataSOurce for rendering it content. The DataSource is always set on the Main report. Everything via designer, no need for coding. So I'd like to see such a possibility in telerik reports. The suggested solution - with the bindings http://www.telerik.com/forums/how-to-bind-the-datasource-of-a-subreport-in-the-designer is technically wrong. It assumes that the child report knows at which level he resides inside the main report. The child report (or it's binding) should have not such info embedded. Let's see on an example. Let's have a dataset: User.Address User.PostalAddress User.Wife.Address User.Wife.PostalAddress The dataset should be bound to the main report. The main report should have 2 sub-reports (address and postal addres). It can have an another sub-report (for wife data) which then would again have 2 sub-reports inside for addresses. Using the technically wrong solution, the addresses for the main user should have a binding expr. like: =ReportItem.Parent.DataObject.xy and the wife's addresses have like: =ReportItem.Parent.Parent.DataObject.xy There is a big problems with such a binding: the child must know the hierarchy of the data. The technically clean solution is to have a dataset assigned to the main report. When adding a sub-report to the main report, via binding we should set the new data-source for the sub report. something like: MainReport.Data = dataSource. SubReportAddress = dataSourceOfTheCurrentReport.Address. SubReportWife = dataSourceOfTheCurrentReport.Wife and inside "wife report" the next sub-report for address address should have a binding again like: SubReportWifesAddress = dataSourceOfTheCurrentReport.Address
The version is encoded twice in each QR code; once at the top right and once mirrored at the bottom left. A comparison of the boxes tells which is the version.
The Reporting tool doesn't mirror the version correctly at the bottom left, and some strict barcode readers don't recognize the barcode correctly.
The JS file with the stringResources shipped with the installation at the following location:
C:\Program Files (x86)\Progress\Telerik Reporting <Release>\Html5\ReportViewer\js
is incorrect, it should be as shown in the Localization - Telerik Reporting article.
Basically, line 9 should be changed to:
; (function (trv, $) {
while lines 178 to 180 should be like this:
trv.sr = $.extend(trv.sr, sr);
}(window.telerikReportViewer = window.telerikReportViewer || {}, jQuery));