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!

I have created a report parameter that accepts null as a value(AllowNull=True) and have set null as the default value by using the expression =Null on the Value property of the report parameter.

This report parameter also has a data source assigned to it so it has available values. Here is a look at the full setup:

When I call the "getReportParameters()" function on the HTML5 Report Viewer, there is an exception thrown in the console that looks as follows:

telerikReportViewer:1 Error: The available values of parameter Parameter1 do not contain Value property that equals null
    at Ae (telerikReportViewer:1:45529)
    at Object.getReportParameters (telerikReportViewer:1:38265)
    at Object.getReportParameters (telerikReportViewer:1:108469)
    at <anonymous>:1:50

I have a main report - "MainReport.trdp" and a report that I use in the detail section of the main report as a subreport twice - "SubReport.trdp".

In "SubReport.trdp", I have a report parameter whose value I use in one of the calculated fields in its data source component.

The calculated field's expression is evaluated based on the report parameter value passed with the SubReport's ReportSource object of the first SubReport item for both subreports.

For example, if I pass the string "A" to the first subreport's parameter and the string "B" to the second, the calculated field in both instances will evaluate based on the first value, in this case -  "A".

The second subreport should evaluate the calculated field based on the value passed to its report parameter, it should not matter if I have the same report rendered as a subreport multiple times and whether a different parameter value is passed to them.

Hello SupportTeam,

when using privateFonts, the WPF-ReportViewer does not use the correct-FontFile when multiple Font-Files are present in the same folder.

The used Graphics-Engine is GDI.

Example 1:

When putting every File in its own Folder it works as expected.

Example 2:

During debugging, we noticed that in case of WPF, the Directory is passed instead of the Full file Path:

In class: Telerik.Reporting.Processing.Common.FontContainer

Best regards

Alexander Schneider

I am using the HTML5 Report Viewer and have a multi-page report. When the report is previewed with the default pageMode setting, where pages are continuously scrollen into, the found search results are correctly highlighted.

However, if I use pageMode="SINGLE_PAGE" in the HTML5 Report Viewer initialization code, and I navigate to page 2 or further, the found results are not highlighted.

I run an ASP.NET Core application that has the functionality to export reports into PDFs in an Azure environment.

There is no way to install additional fonts on Azure so I provide the fonts used in my reports via the "privateFonts" element of the Reporting configuration.

This works for the most part, the font is embedded in the produced PDFs but if I have a textbox with a large text, the text may be cut off when using the Skia engine.

I tested running my application in Docker, I copied the needed fonts in the usr/share/fonts directory of the Docker Linux container, and tried exporting again.

When exporting from Docker, with the fonts installed in the container, the text is not cut off. It seems that there is an issue when the fonts are provided as private fonts.

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

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

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

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

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.

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.

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>

Currently, the VS item templates, and the documentation suggest using app.UseEndpoints for route registration in ASP.NET Core.

It would be better to use top-level route registrations like app.MapControllers() and app.MapControllerRoute() directly.