When a system tells users they should look into the report parameters as the reason the report isn't displaying. It's reasonable for your users to believe you aren't misleading them.
The report viewer error message misleads users. In reality the parameters are correctly configured and it the repot URL could be wrong. Or a variety of other issues are at play; for instance, a problem with you connection string will also return the "Unable to get report parameters" error message. I'd like to see this error message at minimum changed to "report can't display." It's better to throw out a generic message vs having users spend hours or days troubleshooting the report parameters. Better yet a proper catch/validation system put into place please.
However, in my report, the Interactivity options do not show any property for Level. I am only seeing basic properties like Action, BookmarkId, DocumentMapText, TocText, etc.
The Level field is completely missing.
I have projects on .NET Core and I want to use the System.Text.Json serializer that is the new default, but reporting relies on Newtonsoft.Json.
---
ADMIN EDIT
There are two approaches that can be taken right now to solve this:
OPTION 1: define separate endpoints (services, projects) for the different tasks - they can still use the same database layer through a shared project, depending on the architecture you have. This would let you have separated services with the appropriate serializers without custom attributes and code (see below). For example, create a separate project for the reporting REST services.
OPTION 2: add some custom decoration on the endpoints so you can choose which serializer is used on each, you can find some examples here: https://stackoverflow.com/questions/59650907/how-to-configure-two-json-serializers-and-select-the-correct-one-based-on-the-ro - the point being to register a serializer depending on the endpoint based on your own code rather than let the framework put one in for all endpoints.
NOTE: This would be a breaking change.
---
In MSSQL, you may use syntax like 'StoredProcedureName;1' to indicate stored procedure versioning, but it is not yet supported by Telerik Reporting.
I use such syntax and need to remove the version to make this work in Telerik Reporting.
It would be great if you also added support for versioning in MSSQL stored procedures.
We are using the Telerik Reporting component and are very happy
We really wanted to use the Table of Contents component in our reports
The Table of Contents works great but unfortunately does not support right-to-left in Hebrew
I guess for you this is a small fix and for us it will be a big relief
We ask for your help and improve the component for us so that the wonderful Table of Contents supports right-to-left
Thank you
Tamar
Currently, if the SkipBlankPages property is set to True and there is not any significant content in the report, the following message will be displayed in the designer and the viewer: The current data set presented in the report did not produce any significant content, so no pages were generated. If you need to see the whole report content, including blank pages, please contact the report author.
WebReportDesigner (Blazor) - permission to restrict "Build new data connections" and allow to use only "Select from existing data connections".
It isn't required, but would be nice have button "Test connection" in the bottom enabled to verify predefined connection
Currently, when you set SplitWorksheetOnPageBreak to True, the Excel Sheet name is formed from the DocumentName or ReportName and the number of the page.
It would be very helpful if the report authors can manipulate these names with Expressions.
Currently, there is an MCP server that allows for integrating and developing report viewers, report designers, and Reporting REST APIs through Copilot. Consider allowing end users without Telerik Reporting experience to also build reports using AI.
I would like to request the addition of FormulaPrefixCharacters.
I have a .NET project. I tried to add a CS-based report to it using the Visual Studio item template. However, when I opened it, I encountered an error message, which wasn't helpful.
After reaching out to the technical support, I was told that the Visual Studio Report Designer was not supported in .NET projects, and the alternative was either to open the CS-based report through the Standalone Report Designer or use TRDP reports (recommended for new reports) instead.
It would be nice if there were some warning about this, as it would save me some time and confusion, as at first, when I encountered the error message, I took the assumption that something was corrupted with my project.
Images taken with a mobile device are sometimes displayed in PictureBox rotated by 90, 180 or 270 degrees. The reason is that whenever a photo is taken, the device saves its current accelerometer orientation into a corresponding Exif tag with the image metadata, so this info is then read and taken into account by our Report Designer.
Currently, the is permission for disabling saving, but it disables only the "Save" button.
I would like to be able to disable the "Save As" button and keep the "Save" button active, or vice-versa.
This is related to Ticket ID 1699907.
Currently, the WinForm report viewer fetches configuration (specifically the connection string for any named connection strings defined in reports) directly from appsettings.json, however, it would be useful if the report viewer could take into account an injected IConfiguration since there are scenarios where the configuration may not exist in appsettings.json or a preferred or more up to date user selected value has been added to the configuration from a different source (such as a userSettings.json or secrets.json).
Some background of my use case:
I have a desktop WinForms application targeting .NET 8.0. It usesTelerik.Reporting 19.2.25.813 and Telerik.ReportViewer.WinForms 19.2.25.813 to display reports.The reports are TRDX files designed with the 64-bit version of "Report Designer". The report viewer is being displayed in a dedicated WinForm named FrmReport which configures the reportViewer control to use a UriReportSource pointing to the folder on the user's C:\ drive containing the report files. The reports are designed to use a named connection called ReportsConnection which is configured/saved as a shared connection with Alias ReportsConnection in Report Designer.
The default reports connection string is saved in the appsettings.json file. Upon application startup users select a database connection from a list of saved/remembered connections and the desktop WinForms application saves the user selected ReportsConnection to a configuration file named userSettings.json. Both appsettings.json and userSettings.json are configured as sources for IConfiguration with reloadOnChange = true. After a user selects a database connection and the selected connection string is written to userSettings.json, the configuration is reloaded so that the injected IConfiguration from the service container will have the new, user selected value for ReportsConnection. At this point, IConfiguration has the updated the named ReportsConnection with the desired connection string, which almost always differs from the default one defined in appsettings.json.
However, when loading the reportViewer, the reports unconditionally connect to the server and database defined in the default connection string from appsettings.json, not the user-selected connection string even though the injected IConfiguration has the updated user selected connection string.