When using the latest version of the Kendo Default Theme:
<link rel="stylesheet" href="https://unpkg.com/@@progress/kendo-theme-default@latest/dist/all.css" />the export in the Blazor Report viewer does not work.
Meanwhile, you can reference the older kendo CSS styles directly in the view with the ReportViewer. You may leave the new styles referenced on the layout page. It works with:
<link rel="stylesheet" href="https://unpkg.com/@@progress/kendo-theme-default@4.26.0/dist/all.css" />
Issue #1: In WinUI3, for Telerik Report Viewer, when we have a link to URI to open in a new window, it is not working correctly.
Here is a setting in a demo report (Report Catalog):
When clicking to link in control on runtime, we are getting the following error:
This looks like a bug.
Issue #2: Our scenario is the following: We will have some custom links in a report like, "MyApp:Customer/TEST". When we click on that, we need to send that link to our WinUI app, which will let's say navigate to a Customer page after it is clicked in a report. Due to Issue #1, we were not able to test it. Even when Issue #1 is resolved, what is a good way for us to handle the current scenario? I don't want to refresh the report when some link is clicked.
Issue #3. We might have the HTML Text box in a report. When it has a link, it is not clickable. This is another item that looks like a bug.
Can you please help to resolve these 3 issues?
Thanks,
Updating jQuery to 3.6.0 seems to work, however, using Kendo 2022.1.119 appears to break the fonts and some menus in the web report designer.
The rest of our project is using 2022.1.119 so we would like to deploy only one version of Kendo (and jQuery) across our product.
The response to the Get Page request of the REST Service in .NET Core/5/6 doesn't include page size when the paper kind is Custom. This may be the reason why the printing from the WPF Viewer results in blank pages.
When the service is in .NET Framework, the paper size is in the response, and the document is printed correctly.
The XAML rendering extension, used by the WPF Report Viewer, by default checks for invalid characters while writing the XAML page contents. When the data that will be rendered on the page contains invalid Unicode characters, an exception is thrown and the report is not rendered.
The current solution is to introduce a UserFunction that parses the string contents and strips the invalid characters, but implementing and maintaining this approach requires more efforts from the developer.
An option in the XAML Device Information Settings that disables the check for invalid characters, would work in most scenarios without having to write a dedicated UserFunction. By default this option will preserve the current behavior, i.e. the characters checking will be performed, but the developers will have the ability to disable it on their own discretion.
Adding a Parent Group to another Column Group in a Crosstab leads to "Object reference not set to an instance of an object" on report preview. Stack Trace:
Object reference not set to an instance of an object. at Telerik.Reporting.Processing.Table.ForEachCell(Action`1 action) at Telerik.Reporting.Processing.Table.MeasureDataItemContent(IMeasureContext context, SizeLU availableClientSize) at Telerik.Reporting.Processing.DataItem.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.AbsolutePositionLayout.MeasureChildItems(IMeasureContext context, SizeLU availableClientSize) at Telerik.Reporting.Processing.AbsolutePositionLayout.MeasureContent(IMeasureContext context, SizeLU availableClientSize) at Telerik.Reporting.Processing.ReportSectionBase.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)
The following error is thrown when inserting a new column on merged columns in a crosstab/table and then trying to select that column:
"Value cannot be null. Parameter name: components"
The property DataSources is internal in the Report class. When manipulating the datasources of a report it's easier to have access to this collection than to go through all the elements en report parameters to check for datasources
There is nothing really pro outside visual controls for reactJs to many source to many projects could be amazing if telerik create this full set including the report viewer