Getting this error in the browser when trying to preview a report:

Error registering the viewer with the service.
An error has occurred.
Incorrect value (null) deserialized. Make sure you are using CacheStorage inside single-instance application deployment only.

A possible reason is the cache for the Report Server used for previewing reports has become corrupted. A workaround is explained in the Telerik.Reporting.Cache.CacheStorage.AddInSet NullReferenceException KB article.

It will be very convenient for the user to be able to clear the cache directly from the Report Server Manager UI.

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 seems that when you try to open two tabs in the same browser looking at different websites, the browser gets confused about the URL that is sending the request. Issue is related to CORS protocol and HTTP caches.

It sounds like something needs to be changed on the report server so that even if it gets cached it would still allow access when I switch sub domains.  Or something on the viewer side to clear the cache.

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.

Functionality for capturing user activity like executing reports from viewers or through the Report Server Web API.

Could the 'From' email address in Preview Email functionality be self populated from the 'Mail Server' SMTP settings in configuration?

This way the users do not need to a) remember the email address; and b) type it each time they are emailing a report.

Provide the option to save custom report settings in the storage and enable specific rendering device settings based on custom settings.

Example use case:

- on the Report Server - Report view, the user should have a button for report settings;

- this button will open a custom dialog that contains various inputs;

- clicking Save on the custom dialog, the save operation will be handled by the Report Server implementor and the implementor should be able to get the user input and save various settings in the Report Server storage for the selected report;

- on rendering the report through the Preview, Scheduled Task, or Data Alert, the report server engine should invoke a custom event/code that can read the storage report settings and based on them provide rendering device settings to use during the report rendering.

If you set a default value of integer subreport parameter to '3233' or another valid integer, when executing the main report there will be an exception stating that the value for this parameter is not valid and the report processing is canceled. The parameter exists only in the subreport and not in the main report.

The error disappears if the value of the parameter is set with an Expression, for example, '=3233'.

User functions should be visible in Edit Expression editor when editing Report Server's report in Standalone designer.

Considering that the server's configuration was modified to load the custom assembly with user functions as per How to configure Telerik Report Server to use reports with custom functions, there should be no other configurations required.

Dear Mr/Ms,

I'd like to file a feature request: please implement the option to change the report's draft status (true/false) explicitly via the Report Server's UI. It would be a nice feature in case we'd like to test the report in our MVC application, then we'd like to revert it in case any problems.

Reports with resources for different languages should be rendered with the language resources and client culture.

• Preview - render the reports according to the browser settings/language;
• Scheduled Reports and Data Alerts - language/culture option is needed for every recipient;
• Server API - have to accept device info or language/culture option;