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 multiline text in a TextBox item that has its Style > TextAlign set to Center.

It is rendered as expected with the GDI+ graphics engine.

When I switch to the Skia graphics engine in the Standalone Designer .NET, though, some lines are not centered correctly in PDF rendering:

In Preview of the designer, with PNG and OpenXML export the text is shown as expected.

The data member list in "Choose a data member" (step 2) of the objectDataSource wizard in the Web Report Designer does not appear to be in alphabetical order as it is in the Standalone Report Designer.

When there are many data members it is hard to pick the one you want when not ordered alphabetically.

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.

If I render a report that produces zero pages in the Native Angular Report Viewer, the rendering will fail with an exception in the browser console but it won't be caught by the viewer's error event.

This exception breaks the report document generation and it should be caught by this event according to the Handle errors in Telerik Reporting - Telerik Reporting article.

When I try to export a ReportBook to TIFF as explained in Exporting a report to a multi-document format, I receive an exception related to the file '.../report/image.tif' that cannot be created.

When I create the folder '.../report', there is another exception message:

'The process cannot access the file '...\report\image.tif' because it is being used by another process.'

The above error was thrown the second time the ReportProcessor tried to access the 'CreateStream' method from the code snippet in the above article. The 'image.tif' file is created and contains only the first report from the ReportBook.

With version 15.0.21.112 the last exception is not thrown and the 'image.tif' file contains all reports from the ReportBook.

Reproducible in 17.1.23.606 - SRD .NET6

Steps to reproduce the behavior:

1. Open Product Sales report
2. Click on textBox3
3. Select "Split cells" from the context menu.
4. Click "Undo"

Expected behavior
No exceptions
Actual behavior
Table Body has 9 rows but 3 are expected.

Screenshots
Screenshot

After updating to Telerik Reporting v19.0.25.211, the relative path provided to the UriReportSourceResolver is no longer working.

For example, I used to provide only the name of the directory with the reports(e.g. "Reports") to the UriReportSourceResolver, and if there was such a subdirectory inside the project's base directory, the reports were successfully resolved.

This is no longer the case with v19.0.25.211. With this version, I have to provide the absolute path to the "Reports" directory for it to work.

Currently, the Native Angular Report Viewer does not support NodeJS 22. It is restricted to v16-21 of NodeJS and I would have to downgrade to use it.