As a user utilizing the Report Server product, I need to use a single instance of it to serve two or more completely separated divisions/clients so that they do not have access to each other's assets, so that I do not have to make two different deployments of the server and support them. See https://en.wikipedia.org/wiki/Multitenancy

In many cases one can't simply ask users to download an installed report builder. The reports should be buildable in a web based tool.

It would be great if users didn't need to authenticate with two different web applications.

I would use the report server integrated with my current ASP.net website. It would be great if it authenticated and authorized users based on the same roles also.

Import sql server reporting (rdl) files

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 when the report is run through the web or designer the report runs fine as the logged in user identity is available. However, when the report is scheduled user.identity.name returns null. This translates to no way to customize a report scheduled to run differently from a logged in user e.g. logged in user has row/data restrictions can be triggered by the user identity while when scheduling mgiht wish to expose more information.

When connected to Report Server, double-clicking a child member of an expandable field (e.g. Year under a DateTime column) in the Expression Editor inserts an incorrect expression: Fields.Year instead of Fields.ActualField.Year.

Have the ability for reports to be generated at defined intervals and delivered to one or more defined destinations - together. For example, a monthly report pack (consisting of a number of reports) can be sent to a client with all reports attached to the single email or compressed into a single zip file, or merged into a single Excel workbook, or PDF file before delivery.

Current Behavior

Telerik Report Server currently limits authentication to a single federation provider. Organizations requiring multiple identity providers must implement a custom authentication provider as a workaround.

Requested Enhancement

Allow configuration of multiple federation providers simultaneously within the Report Server administration interface, enabling users to authenticate via any configured IdP without custom development.

Use Case

• Organizations with multiple Azure AD/Entra ID tenants (e.g., separate tenants for different business units, subsidiaries, or during M&A transitions)
• Hybrid environments requiring both corporate IdP and partner/vendor IdP access
• Migration scenarios where legacy and new identity providers must coexist temporarily
• Multi-client SaaS deployments where each client uses their own identity provider

Proposed Implementation

• Admin UI to add/remove multiple SAML 2.0, OpenID Connect, or WS-Federation providers
• Provider selection presented at login (dropdown or separate buttons per IdP). Optional as could just as well aut select based on login.

Business Impact

The current single-provider limitation forces organizations into complex custom provider implementations, increasing maintenance burden and potential security risks. Native multi-provider support would reduce implementation complexity and align with modern enterprise identity management requirements.

After migrating from the old Report Server to the new Report Server for .NET, the previously existing ADFS users show up as "Federation" users in the new server, which is incorrect, since the new server uses Entra ID authentication instead of ADFS.

I'm using Crystal Enterprise for a longtime, and would like to replace it with that tool.
 On of the most useful feature is scheduling (for time-hungry reports, that takes more than 20 minutes to be generated).

It will be a plus if you add:
* The ability to choose the Execution start time, and frequancy; and to enable or disable the schedule job without lossing it.
* Add a menu item called "Schedule Jobs", to view all schedule jobs of any accessible report (per profile; Admin can see all categories by profiles).
* The ability to execute on-demond (execute disabled or enabled schedules for prepared parameters).
* The ability to sign the generated PDF.
* The ability to send generated PDF to mail (one or more), and to set the mail subject and body.
* nerated PDF to folder (local, remote with auth) or FTP.The ability to save the ge
* The ability to view schedule execution history, and view its result; and Add option to clear old results.
* No "time out" for longer generation process.
* Schedule jobs queued per user profiles;
* Admin can set priority to user profiles (to execute queued jobs), and can cancel jobs.

It recently became apparent to us that there are multiple templates for sending email. There is the one that can be customized but it only get customized for internal users. There is also a separate template for external users and it cannot be customized and is common across all reports.

All templates need to be customization for each report. Since the Report Server is designed to send to anyone and the licenses are controlled by who can create reports, it makes the ability to send report to users extremely limited. 

> Ability to build directories for storing reports; and allow assigning user permissions per user.
> So, Application A, will have its reports in Directory A; Application B, will have its reports in Directory B.
> It will be a plus if you support a hierarchy or sub-directories.
> It will be a plus if you add user group, to be assign by group.

Add per hour scheduling with filters for hours and days on which to execute.

Our company has many different profit and loss groups which act as mini-companies that share customers, vendors & transport companies. Each group doesn't want the other groups to view reports relating to their contracts, shipments & invoices.

This has been one of the failing of the Microsoft Report Server. I would have to pass in the query string the groupid. Any group could manipulate the query string to see other groups reports. So all reports are built in the web app with the groupid setup in their profile.

A solution to our type of business reporting needs would be helpful. Otherwise we will just roll our own reports in the next version also.

Would be nice to add support for CRON expressions when setting up the schedule of a task or alert. CRON expressions are widely used, for example in AWS, Oracle, Quartz, etc.

In the production environment, there is no option to clear the Redis database after each redeploying/restarting of the applications (ex. k8s with many pods).

The are many reasons:

• this database can be used for other purposes, but you deprecate RedisStorage with a separate database selection
• more complex deploy/restart operations with additional steps to clear Redis
• users can use Reporting at this moment

Please add TTL option for RedisStorage in ReportServiceConfiguration

ability to pass parameter value to report using url exapmle  
http://localhost:83/Report/Preview/170705-3ff1?TestyYear=2015

Provide the ability to re-brand the Report Server to better fit our corporate identity and better integrate (styling-wise) with our existing apps.

I extensively use sub reports with drill-down, drill-through actions and to fetch data, into the main report, extracted from different datasets based on a set of certain parameters.

When I upload these reports to the server, I assign main and sub reports to two separate categories 'Main' and 'SubR' so that I can manage reports and users' permissions accordingly.

Currently, it is not possible to 'hide' the reports under 'SubR' category for a user so that all the sub reports are hidden from view, leaving visibility of main reports only for that user.

I tried by restricting user's access to the category 'SubR' so that sub reports are not visible in the list and avoid confusion from user's perspective. But when I restrict user's access to the category 'SubR', all the main reports that contain sub reports do not run correctly and start displaying 'unable to access subreport1...' error. The same error comes up if I have included a report in the main report, accessible by drill-through action.

I would like to request for a functionality to 'Hide / Display' reports in conjunction with 'Read' access to the reports. This will provide further granularity to the way the reports can be made accessible and still be hidden from view.