Currently, the Shape item in the Web Report Designer exposes a smaller set of predefined shapes than the Standalone/Visual Studio designers.

For example, the Square type is not available in the Web Report Designer, and I have to configure it manually through the Shape item settings.

The Whitelabeling option are extremely limited.

I would like to see more customization available like removing the sidebar completely, or based on user settings / roles - as well as the top title bar (where logo is).

Customizable themes would go a long way.

Being able to integrate the existing report server pages into our own website would cut down on a lot of work.

Currently, the Report Server is installed with binding only to HTTP-type sites. This may break a Report Server site bound to an HTTPS site after upgrading to a new version. It is necessary to add the binding to HTTPS manually after each upgrade.

It would be great if there is an option for binding to HTTPS with the installation and if all the bindings can be preserved after upgrading.

The Report Server is localizable. However, its viewer is not.

The viewer cannot be customized either. For example, if you want to make the default View mode PrintPreview.

The above require changes in the CSHTML template of the Preview, which would be reset upon the Report Server upgrade.

It would be great if the customization and localization of the Report Server Viewers became part of the configuration, allowing them to be preserved between upgrades.

The Report Server is localizable. However, its viewer is not.

The localization of the viewer requires adding a new JavaScript file with the translation and referencing it in the CSHTML template of the Preview, which would be reset upon the Report Server upgrade.

It would be great if the localization of the Report Server Viewers became part of the configuration, allowing them to be preserved between upgrades.

We have a scenario where some groups need to have reporting info that is not visible to other users on the Report Server instance.  I can assign permission limiting access to report categories and data connections, but I don't see a way to limit shared data sources. 

Imagine, for example, a scenario where payroll wants to include an ADP data feed in their reports and they want to save it as SDSX to use in multiple places.  As far as I can tell, all other report editors on the server can now load and use that SDS.

I should be able to determine what SDSX files each user can access in the same way that I can for specific reports.

The Report Server mail templates have a variable named "link" which should provide a link to the exported document for the email receiver.

However, this link does not use the Report Server's public address set through IIS, instead, the link uses the "http://localhost:83" as a base URL for the link.

Please correct the behavior and/or allow for changing the links' base URL.

Currently, the POST api/reportserver/v2/documents endpoint is available only for the standard version of the Report Server.

Consider adding it to Report Server for .NET as well.

The assemblyReferences, typeReferences, and typeValidation configuration elements are not respected from the TelerikReporting.config files of Report Server Manager and ServiceAgent.

The same settings are respected when set in the corresponding Web.config and Telerik.ReportServer.ServiceAgent.exe.config.

When I try to use the Report Server for .NET 2025 Q1 in a Docker container, I get the following error in the logs:

"An error occurred while checking the licenseResult: The value cannot be an empty string. (Parameter 'path')."

The error does not seem to prevent the Report Server Manager from remaining functional.

Hi Team,

Currently when Report Server has whitelabeling enabled, the browser tab will still show "Page | Telerik Report Server". This request is to allow us to set a value for the 2nd half of the page title.

I see this is applied by using the @ViewBag.Title, my request is to have a field in the Whitelabeling settings page for a brand name in the title. This could be combined with the page name to have a customized title. For example "Page Name | Whitelabeled Name".

Here's a visual example to explain further

Thank you,

Rick

We need to send emails to specific people only when Errors occur in scheduled reports. They shouldn't receive the scheduled reports when there are no errors.

For example, there may be a new user role added for this purpose.

Hi Team,

This feature request is to ask that a capability be added to Report Server that restricts certain administrative functionality to only be allowed on predefined subnets (e.g. adding new users, data sources, etc.).

Thank you,

Amish