Hello,
I am working on Blazor reporting project and I have described the situation already in this post:
https://www.telerik.com/forums/report-viewer-and-web-designer-in-blazor#zGr6FO2mDEmkfLWIP_T_9A
Please add Blazor ReportDesigner wrapping Your HTML designer and use .NET 5 js/css isolation to manage js/css loading by the component itself and not globally.
Thank You
Marek Ištvánek
I am working on a report in the .NET Report Designer that takes time parameters. I am looking for a way to replace the DatePicker that is used in the Report Designer parameters section with the DateTimePicker, but I've been told by support that there is no way to do that.
At a minimum, I need a way to specify which picker (Date, Time or DateTime) that the Designer should use. Being able to specify a format would be helpful also. Ideally the stand alone designer would provide a way to customize and view a custom template that is developed for the HTML5 Report Viewer.
I'm stilling trying to figure out what I have to do, but it appears every time a modify the report I'm not going to be able to view it in the Designer and instead I'm going to have to view it in the Report Viewer in the main application, which will be a much slower and more cumbersome process.
The following exception is thrown when rendering a report with enabled Accessibility to PDF with Skia if the report has a Table containing an HtmlTextBox:
Telerik.ReportDesigner.Net Error: 0 : System.NullReferenceException: Object reference not set to an instance of an object.
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.TryAttachToParentNode(ProcessingInstanceIdentifier id, PdfOrderedReference element, Int32 rowIndex, Int32 columnIndex)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.TryAttachToParentNode(IProcessingElement processingElement, IProcessingElement parentProcessingElement, PdfOrderedReference taggedElementReference)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AttachNonLeafNode(LayoutElement element, PdfOrderedReference taggedElementReference)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AttachNodeToTree(AccessibilityPdfElement pdfElementType, PdfOrderedReference taggedObjectReference)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.InitTaggedElement(AccessibilityPdfElement pdfElementType)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.AddParagraphElement(ITableCell element)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.Visit(HtmlTextBox htmlTextBox)
at Telerik.Reporting.Processing.HtmlTextBox.Accept(ProcessingElementVisitor visitor)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.AccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
at Telerik.Reporting.Writing.VisualElementWriter`1.StartWriteAccessibilityItem(ReportItemBase item, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.VisualElementWriter`1.WriteClientFocusableItems(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.VisualElementWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.ReportItemBaseWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.ElementWriter`1.Telerik.Reporting.Writing.IElementWriter.StartWrite(LayoutElement element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.WriteStartOperationsDispatcher.Write(IElementWriter writer, LayoutElement element, ElementPageInfo pageInfo, DocumentWriter documentWriter)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Write(IElementWriter writer, LayoutElement element)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(HtmlTextBox htmlTextBox)
at Telerik.Reporting.Processing.HtmlTextBox.Accept(ProcessingElementVisitor visitor)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.DispatchWriteOperation(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.BaseRendering.PageHandler.Telerik.Reporting.Paging.IPageHandler.StartElement(LayoutElement element, ElementPageInfo info)
at Telerik.Reporting.Paging.PageStartElement.OutputToPage(IPageHandler handler)
at Telerik.Reporting.Paging.PageElementsLayer.OutputToPage(IPageHandler handler)
at Telerik.Reporting.Paging.PageContent.Output(IPageHandler handler)
at Telerik.Reporting.Paging.PageCompositionBase.OutputPageContent(Stopwatch stopwatchOutputContent, PageContent pageContent)
at Telerik.Reporting.Paging.PageCompositionBase.<>c__DisplayClass124_0.<CreatePageContentOutputTask>b__0()
Telerik.ReportDesigner.Net Error: 0 : An error has occurred while rendering the report: System.OperationCanceledException: The operation was canceled.
at System.Threading.CancellationToken.ThrowOperationCanceledException()
at System.Threading.ManualResetEventSlim.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.SpinThenBlockingWait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.InternalWaitCore(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at System.Threading.Tasks.Task.Wait(CancellationToken cancellationToken)
at Telerik.Reporting.Paging.PageCompositionBase.SeparateThreadOutputBehavior.Finish()
at Telerik.Reporting.Paging.PageCompositionBase.CreatePages()
at Telerik.Reporting.Paging.PagerBase.Telerik.Reporting.Paging.IPager.CreatePages(IPageHandler handler, LayoutElement root)
at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)A similar error is thrown when rendering with GDI+.
Hi Team,
When using the WPF ReportViewer, Reporting appears to only fetch settings from appsetting.json, and ignores any other values coming from things like secrets.json, or any other configuration builder.
Please see the following forum thread, where Lance replied with a test that verifies none of the values from secrets.json were accessible to Reporting even though they are in the global Configuration (at 13 Sep 2024, 12:34 PM (ET) => https://www.telerik.com/forums/simple-wpf-reportviewer-example). Reporting only respected appsettings.json.
Proposed Solution
Telerik Reporting should accept whatever implementation of IConfiguration I choose. Ideally, when setting up my application, there should be one line that looks something like this:settings.AddTelerikReporting(configuration);
That allows me to pass the full view of the Configuration to Reporting that allows it to see more than what might only might be in appsettings.json (secrets, imported configurations, etc).
Thank you,
Brad
We work in a project with more than 100 parameters. The parameters are sorted in the order we added them.
It is hard to look for a parameter when we need to do a change. A right click "sort" would be great.
I understand that the ReportViewer has a very different paradigm from, say, the RadGridView. However, I believe they should and could be much more similar. With some fairly minor tweaks ReportViewer could be made to be a proper member of the C#/XAML/MVVM environment. Particularly what is needed is a binding to the data source, just like RadGridView's "ItemsSource".
I've begun a discussion in the forum about this topic at https://www.telerik.com/forums/reporting-and-mvvm. With Momchil's help I was able to create a workable solution for my scenario, but it required code that, in my opinion, I shouldn't have to write.
I'd be more that willing to chat about this further and provide more thoughts and details, but since we've made it all the way to 2024 without this being raised, I tend to assume the needs I've expressed may not be as universal as I'd assumed they would be.
Thanks!
Hi,
For our product we were looking into adding additional Request headers to the HTTP requests made by the Telerik Reporting library to the webservice data endpoints for our reports.
We tried adding the headers through a custom DelegatingHandler or HttpClientHandler, but found those were not being picked up.
Not when using the Web Report Designer or Blazor Report Viewer.
Any change we could register such a DelegatingHandler or HttpClientHandler?
Or any other suggestion on a how to add additional headers to the outgoing requests?
Setting the Style > BackgroundImage property of the Linear Gauge > Indicator throws the following error:
This doesn't let me customize the Indicator of the Gauge.
When rendering a report to PDF with the accessibility feature enabled - PDF Device Information Settings at a glance - Telerik Reporting, if there is a table/list/crosstab item that contains an item with a Navigate To Bookmark action pointing to the same BookmarkId, the document won't be rendered because of the following error:
System.ArgumentException: An item with the same key has already been added. Key: (table1) Table X=3810 Y=762 Width=2990 Height=1830
at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.Visit(Table table)
at Telerik.Reporting.Processing.Table.Accept(ProcessingElementVisitor visitor)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.AccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
at Telerik.Reporting.Pdf.PdfAccessibilityElementWriter.StartWrite(ReportItemBase element, Int32& index)
at Telerik.Reporting.Writing.VisualElementWriter`1.StartWriteAccessibilityItem(ReportItemBase item, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.VisualElementWriter`1.WriteClientFocusableItems(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.VisualElementWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.ReportItemBaseWriter`1.StartWrite(T element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.ElementWriter`1.Telerik.Reporting.Writing.IElementWriter.StartWrite(LayoutElement element, ElementPageInfo pageInfo, DocumentWriter writer)
at Telerik.Reporting.Writing.WriteStartOperationsDispatcher.Write(IElementWriter writer, LayoutElement element, ElementPageInfo pageInfo, DocumentWriter documentWriter)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Write(IElementWriter writer, LayoutElement element)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.Visit(Table table)
at Telerik.Reporting.Processing.Table.Accept(ProcessingElementVisitor visitor)
at Telerik.Reporting.Processing.ProcessingElementVisitor.Visit(LayoutElement element)
at Telerik.Reporting.Writing.WriteOperationsDispatcher.DispatchWriteOperation(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.Writing.DocumentWriter.Telerik.Reporting.BaseRendering.IWriter.WriteStartElement(LayoutElement element, ElementPageInfo pageInfo)
at Telerik.Reporting.BaseRendering.PageHandler.Telerik.Reporting.Paging.IPageHandler.StartElement(LayoutElement element, ElementPageInfo info)
at Telerik.Reporting.Paging.PageStartElement.OutputToPage(IPageHandler handler)
at Telerik.Reporting.Paging.PageElementsLayer.OutputToPage(IPageHandler handler)
at Telerik.Reporting.Paging.PageContent.Output(IPageHandler handler)
at Telerik.Reporting.Paging.PageCompositionBase.OutputPageContent(Stopwatch stopwatchOutputContent, PageContent pageContent)
at Telerik.Reporting.Paging.PageCompositionBase.<>c__DisplayClass124_0.<CreatePageContentOutputTask>b__0()
When the reporting service fails to generate a report document, the Get Document Info request returns a 500 response with the error message thrown from within the reporting engine. However, instead of displaying the error message in the viewport, the Native Blazor Report Viewer displays a message falsely suggesting that the report is still being rendered when the rendering has, in fact, failed.
In the Standalone Report Designer, collection editors, such as the ReportParameter Collection Editor, do not show the context menu when a property is right-clicked, and resetting property values through such windows is not possible.
The Properties window of the designer illustrates the expected behavior.
The Editor-Control for the HTMLTextBox does not use the localized values from the WebReportDesignerStrings.xx.js.
When the Blazor Web Report Designer is closed and then reopened, some of its resources are not loaded the second time around, causing the resize handles to break.
Making sure the following resources are always loaded on the web designer page, resolves the issue.
- <script src="/api/reportdesigner/designerresources/ext_js/jquery.ui-1.12.1.min.js/"></script>
- <link type="text/css" rel="stylesheet" href="/api/reportdesigner/designerresources/ext_styles/jquery.ui-1.12.1.min.css/">
When the latest Kendo UI version is used, the ellipsis in the Web Report Designer's Report Explorer tree are invisible, and the context menus of some report items cannot be opened.
For example, adding shared data sources to a report is not possible because this functionality is accessible through the context menu of the [Shared Data Sources] collection in the explorer tree.
Expected behavior:
Actual behavior:
To work around the issue, use the 2022.3.913 Kendo UI version on the Web Report Designer page.
When I enable accessibility in the Angular Report Viewer, based on the HTML5 Report Viewer, I get the following console error:
Uncaught TypeError: Cannot read properties of undefined (reading '_controller')
at telerikReportViewer:1:15863
at Ce. (telerikReportViewer:1:16167)
at Ce.n (telerikReportViewer:1:26372)
at Ce.trigger (telerikReportViewer:1:26686)
at ce (telerikReportViewer:1:32782)
at Object.updateUI (telerikReportViewer:1:43789)
at telerikReportViewer:1:93236The report viewer continues being functional despite the error but accessibility text is missing for page number, export, and buttons(incl. parameters area).
I have projects on .NET Core and I want to use the System.Text.Json serializer that is the new default, but reporting relies on Newtonsoft.Json.
---
ADMIN EDIT
There are two approaches that can be taken right now to solve this:
OPTION 1: define separate endpoints (services, projects) for the different tasks - they can still use the same database layer through a shared project, depending on the architecture you have. This would let you have separated services with the appropriate serializers without custom attributes and code (see below). For example, create a separate project for the reporting REST services.
OPTION 2: add some custom decoration on the endpoints so you can choose which serializer is used on each, you can find some examples here: https://stackoverflow.com/questions/59650907/how-to-configure-two-json-serializers-and-select-the-correct-one-based-on-the-ro - the point being to register a serializer depending on the endpoint based on your own code rather than let the framework put one in for all endpoints.
NOTE: This would be a breaking change.
---
In the latest Reporting version, the interface of the report viewer allows users to set the value of a multiselect report parameter to an empty collection but not make it null.
In some scenarios, reports rely on parameters being null to filter their data and this makes them unusable in the latest version.