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?

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

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

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()

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/">

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.

According to the HTML5 Report Viewer documentation, the persistSession property of the viewer should be set to false by default.

This is not the case for the HTML5 WebForms Report Viewer, the value of its PersistSession property is true by default.

Since the HTML5 WebForms Report Viewer is a wrapper of the HTML5 Report Viewer, it should have the same default values.

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:93236

The report viewer continues being functional despite the error but accessibility text is missing for page number, export, and buttons(incl. parameters area).

Telerik.Reporting.nupkg has a dependency on ResXResourceReader.NetStandard.

Our 3rd party security audit has found the missing Digital Signature of this DLL. A digital signature would aid in verifying its authenticity and integrity.

The labels of the Send Mail form in the HTML5 Report Viewer and its wrappers do not conform to accessibility standards. They refer to form fields using the field's name attribute instead of the id attribute.

Telerik,

This is a feature request to add the ability to override a connection itself and not just the connection string.

The motivation behind this is for IAM based authentication, where usernames and passwords are no longer used but usernames and short lived tokens are.

Many database providers provide a Factory or Builder to allow a Connect to be built that allows the password to be requested when needed. In the case of Postgres, this is the NpgsqlDataSourceBuilder class.

I'm not sure what the contract would look like to achieve this, but setting the connection itself, one way, shape, or form, is greatly needed.

Thanks,

Shawn

When rendering a report that displays an image through the PictureBox item with binary data in multiple threads within a Docker container, the following error is thrown:

Message=Concurrent operations from multiple threads on this type are not supported.
  Source=DockerBlazorApp
  StackTrace:
   at Test.Reporting.Services.ReportService.<>c.<RenderReport>b__4_0(Object innerSender, ErrorEventArgs eventArgs) in C:\Users\dnikolov\Downloads\dockerblazortestappfortelerik\DockerBlazorTestAppForTelerik\DockerBlazorApp\Services\ReportService.cs:line 49
   at Telerik.Reporting.Report.OnError(Object sender, ErrorEventArgs e)
   at Telerik.Reporting.Report.RaiseError(Object sender, ErrorEventArgs e)
   at Telerik.Reporting.Processing.Report.RaiseReportError(ProcessingElement sender, ErrorEventArgs args)
   at Telerik.Reporting.Processing.Report.RaiseError(ProcessingElement sender, Exception exception)
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)
   at Telerik.Reporting.Processing.ReportSectionBase.ProcessItem()
   at Telerik.Reporting.Processing.DetailSection.ProcessItem()
   at Telerik.Reporting.Processing.ReportItemBase.ProcessElement()
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)

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.

In Telerik Reporting versions before 18.1.24.514, I could change the order of items in a section by dragging an item up or down in the Report Explorer list.

If I try that now, nothing seems to happen on the screen. Dragging does not appear to change the position of an item in Report Explorer; the item appears to be fixed in place.  However, if I close the report and reopen it, the position of the item may have changed.

The same happens if I use Send To Back/Brink to Front on an item.  The new item position is not updated in the Report Explorer. 

I use cascading parameters and need to specify their Text property with an Expression, as the label should be translated through a User Function. My parameters shouldn't have values initially.

The problem is that the dependent parameter's Text Expression is not evaluated when the report is first displayed by the designer or viewer. The label shows the Expression instead.

If I make the independent parameter Nullable, the issue doesn't occur, but I prefer not to allow Null values.

The problem is shown in the linked muted video.