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

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.

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.

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.  

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 standalone designer, it would be helpful if you could drag and drop the column headers to reorder.  At present you have to add a new column and delete the old one, remembering to copy all properties.

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.

Actually Axis title can move only on his specific axis.

For example, x-axis title can move left to right and y-axis title can move up to down.

But in same cases, like mine, where the axis are not on the edge of the chart (because it involves negative x and y values and the intersection is in the middle of the field) it is necessary to move the x-axis title up and down to be next to the x-axis position, or to move y-axis left/right to be next to the y-axis position.

Feature request: allow axis titles to be moved on both axis and not only one.

In attach you'll find a screen that shows the desired result.

Best regards

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)

Hi Support team,

On ServerSide, when using a CultureInfo, with a NumberSeperator different then '.', e.g. CultrerInfo("de-DE"), it is not possible to Save a report.

It seems it is internally converted to a string based value and gets the different seperator and than can not be casted/converted back to double.

Best regards

Alexander Schneider

System Development | Loy & Hutz Solutions GmbH

I am using the NPM package [email protected] together with @progress/telerik-angular-native-report-viewer26.25.521. The latter has the following peer dependency listed in its `package.json`:

"rxjs": "^6.5.3 || ^7.4.0"

Version 6.6.7 is within this range, but when running the application, I get errors, such as:

Error: export 'take' (imported as 'take') was not found in 'rxjs

My project uses the following two dependencies:

• Telerik.UI.for.Blazor (v9.1.0)
• Telerik.ReportViewer.BlazorNative (v19.1.25.716)

However, when I build my application and navigate to the page of the Native Blazor report viewer, the following error is thrown:

“Telerik.Blazor.Components.TelerikWindow does not have a property matching the name ‘Centered’.” at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.ThrowForUnknownIncomingParameterName(Type targetType, String parameterName) at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.SetProperties(ParameterView& parameters, Object target) at Microsoft.AspNetCore.Components.ParameterView.SetParameterProperties(Object target) at Microsoft.AspNetCore.Components.ComponentBase.SetParametersAsync(ParameterView parameters) at Telerik.Blazor.Components.TelerikWindow.SetParametersAsync(ParameterView parameters) at Microsoft.AspNetCore.Components.Rendering.ComponentState.SupplyCombinedParameters(ParameterView directAndCascadingParameters)

We'd like to have a settable property on the web designer and report viewer which takes a function which returns an access token.
This way a new access token can be requested by the designer/viewer when the current one expires.

This is usually used in the following way:

1. Implement a function with signature "string GetAccessToken()"
2. Set that function to the property AccessTokenProvider of the designer/viewer
3. Designer/Viewer wants to make a request and fetches and caches the access token
4. Designer/Viewer uses that access token until it hits a 401 upon which
   1. The Cached access token is cleared
   2. A new Access token is fetched from AccessTokenProvider and then cached
   3. Retry the request with the new access token
   4. Should the retry also fail return the failure

Should the above be to specific/inflexible:
Instead of caching the access token, call AccessTokenProvider for every fetch but also provide an additional parameter with the "reason" for the call, so the implementer of AccessTokenProvider can decide themselves when to return a cached AccessToken or generate a new one.

Hi

Currently, when referencing an assembly from appsettings.json in telerikReporting:assemblyReferences  , the Object Data Source wizard in Telerik Web Reporting displays all namespaces from that assembly, even if only one class is marked with [DataObject]. This results in unnecessary namespace clutter and can confuse report designers, especially in large projects where only a single data object is intended for reporting. See screenshots below:

Please provide a way to control which namespaces and/or classes are visible in the Object Data Source wizard. Possible solutions could include:
•    Only displaying namespaces that contain [DataObject] classes (filtering namspaces with no elments to display)
•    Allowing explicit inclusion/exclusion of namespaces or classes via configuration (e.g., in appsettings.json).
•    Supporting an attribute (such as [Browsable(false)] or a new custom attribute) to hide specific classes or namespaces from the wizard UI.

Thank you for considering this improvement!