My use case is a multi-select parameter that is based on a dataset; and the dataset is filtered by 2 other parameters.

The dependent parameter editor is shown as a SpinButton rather than a multi-select editor in the Blazor Native Report Viewer:

When exporting a report to Excel with the UseExtendedFormatting parameter set to False, the Standard DateTime Format Strings are hard coded as custom formats in the generated XLS/XLSX document.

The custom formats correspond to the current regional settings or, if the report is rendered with a specific culture, the default date format strings for the selected culture.  

While customising templates/CSS, I noticed the .trv-parameters-wrapper div as follows:

<div tabindex="300" class="trv-parameters-wrapper" aria-label="Parameters area. Contains 4 parameters.">
<div class="trv-parameter-container k-card"></div>
</div>

this type filteration controllers not displaying in report (version - 18.0.24.130)

Hi Team,

Currently, the DatabaseCacheConfigurator.exe tool seems to be Windows-only. Can you please compile this to be cross platform compatible? I am on macOS and cannot use any Windows tooling.

Thank you,

Frank

We use WPF Report Viewer in our application. For testing, validation, and automation purposes, we need to:

• Uniquely identify each element in the XAML rendered report contents to support automation.
• Prevent the element ID changes. The generated item IDs must remain consistent as long as the report definition is not changed.

When the report contains SVG images with Arc segments, the rendering with Skia may result in the following exception:

Telerik.ReportDesigner.Net Error: 0 : System.InvalidOperationException: Invalid image data.
 ---> Telerik.Drawing.Skia.Exceptions.SkiaNotSupportedException: Exception of type 'Telerik.Drawing.Skia.Exceptions.SkiaNotSupportedException' was thrown.
   at Telerik.Drawing.Skia.Drawing2D.GraphicsPath.AddArc(RectangleF rect, Single startAngle, Single sweepAngle)
   at Telerik.Reporting.Svg.SvgRectangle.Path(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgVisualElement.Render(ISvgRenderer renderer, Boolean renderFilter)
   at Telerik.Reporting.Svg.SvgVisualElement.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgRectangle.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgElement.RenderChildren(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgElement.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgFragment.Render(ISvgRenderer renderer)
   at Telerik.Reporting.Svg.SvgDocument.Draw(ISvgRenderer renderer, ISvgBoundable boundable)
   at Telerik.Reporting.Svg.SvgDocument.Draw(Int32 rasterWidth, Int32 rasterHeight)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.CreateBitmapImage(RadSvgImage svg, Size targetSizePx)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.DrawImage(RadSvgImage svg, CreateImageContext context)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.CreateImageCore(CreateImageContext context)
   at Telerik.Reporting.Processing.Imaging.ImageItemBase.CreateImage(CreateImageContext context)

If I set the ReportSource to the Native Blazor Report Viewer using @bind directive, for example:

@bind-ReportSource="@ReportSource"

ReportSource="@(new ReportSourceOptions { ... })"

It causes the viewer to go into a loop of trying to set the ReportSource, and it never renders the report.

Hi Team,

I have a request for being able to add the `User-Agent` header to reporting calls. We've ran into some image hosting sites that will not resolve image links properly if the user-agent is not present in the request and returns a 403 Forbidden error. Any browser that passes the user-agent parameter can resolve this link.

https://cms5.revize.com/revize/cityofwillmar/_assets_/images/logo.png

But telerik will return this error:

Telerik.ReportDesigner.exe Error: 0 : An exception has occurred while processing 'pictureBox1' item:
System.Net.WebException: The remote server returned an error: (403) Forbidden.
   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
   at System.Net.WebClient.DownloadData(Uri address)
   at Telerik.Reporting.Processing.Imaging.ImageUtils.LoadData(String filePath)
   at Telerik.Reporting.Processing.Imaging.UrlImageItem.CreateUnderlyingImageItem()
   at Telerik.Reporting.Processing.Imaging.UrlImageItem.get_UnderlyingImageItem()
   at Telerik.Reporting.Processing.Imaging.UrlImageItem.CreateImageInfo()
   at Telerik.Reporting.Processing.Imaging.IImageInfoMapExtensions.StoreImageData(IImageInfoMap imageInfoMap, IImageItem imageItem, ICache cache)
   at Telerik.Reporting.Processing.PictureBox.ResolveImage(Object value)
   at Telerik.Reporting.Processing.ReportItemBase.ProcessElement()
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)

Currently, the only way around this is to fetch the images with a custom user function and returns the images to the Reporting Engine as a byte array or other supported format. It's a lot of overhead for something that could simply be toggled on an off, so I think this would be a nice feature addition. 

Thanks,
J.T.

Hi Telerik Team,

We are experiencing an issue related to tooltips in PDF exports from Telerik Reporting.
When we enable tooltips using the ViewerRenderToolTips setting both at the report level and through the device info in the report service, tooltips are appearing in the exported PDF—but they are being rendered as text annotations, not as normal tooltips.

Issue:
In the resulting PDF, tooltips are rendered as Text Annotations, which:

1.Appear as popups or sticky notes on mouse hover/click
2.Are not the standard tooltip experience expected by users
3.May affect accessibility compliance and user readability

Expected Behavior:
Tooltips should appear as standard PDF tooltips (like browser-style hover text) instead of annotations.

If I set both the "EnableAccessibility" and "ViewerRenderToolTips" device info settings to true, the generated PDF document is corrupted.

Greetings,

Telerik.Reporting version: 19.1.25.521

ASP.NET Web Forms

Our team recently had a some trouble understanding the behavior of the ReportViewer.ParametersArea and the property "ParametersAreaVisible". Our desire was to hide this to the end user because the ParametersArea should not be fiddled with directly by the our end users; sensitive data could be accessed. Setting this to false does not stop the render of the ParametersArea. Typically setting the property on a control in ASP.NET Web Forms means the control will not render to the page. So having a property named "ParametersAreaVisible" is misleading in my opinion. I know the ParametersArea is thought as a benefit to the end user but in our case we do not desire this.

My feature request is to add a new property "DisableParameterArea" to the ReportViewer that causes the ParametersArea to not render to the ReportViewer.

Thank you

White space appears between different rows. Depending on the zoom level it could happen on one or more rows.

I will attach a report example to this message.

The Web Report Designer does not entirely comply with CSP standards, necessitating the use of the 'unsafe-eval' directive in our CSP policies to enable its functionality.

This directive poses significant security risks and undermines the purpose of implementing CSP in the first place. Please remove this requirement.

When I drag a data field from a DataSource component to the Report details section in the Standalone Report Designer, the Report > DataSource property is set automatically to the corresponding DataSource component.

In the Web Report Designer, when I drag a data field, the Report > DataSource property remains empty, and the Preview shows an empty report. It would be very helpful the same functionality to be introduced also in the Web Designer.

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.

---