We often receive feedback regarding hard/impossible editing of reports after they are exported to Word format. The existing rendering mechanism will produce Word tables which are harder for manual editing - http://docs.telerik.com/reporting/designing-reports-considerations-word Let us know in comments about your experience with editing reports exported to Word format so we can understand more clearly what is required from Reporting Word rendering extention.
It could be userfull to have a way to dynamically prompt for user name and password for the database connection. The proposed solution to put the connection string in a report parameter exposes sensitive information. It could be an option in the "Configure SQL Data Source" where we could set a checkbox as "Prompt for user name and password". At the end, everything would be saved with the report definition except the user name and password. On the report rendering, the user name and password will raised a dialog box for user name and password for the report.
The XAML rendering extension, used by the WPF Report Viewer, by default checks for invalid characters while writing the XAML page contents. When the data that will be rendered on the page contains invalid Unicode characters, an exception is thrown and the report is not rendered.
The current solution is to introduce a UserFunction that parses the string contents and strips the invalid characters, but implementing and maintaining this approach requires more efforts from the developer.
An option in the XAML Device Information Settings that disables the check for invalid characters, would work in most scenarios without having to write a dedicated UserFunction. By default this option will preserve the current behavior, i.e. the characters checking will be performed, but the developers will have the ability to disable it on their own discretion.
The property DataSources is internal in the Report class. When manipulating the datasources of a report it's easier to have access to this collection than to go through all the elements en report parameters to check for datasources
We use WebServiceDataSource with OData query in our reports. Sometimes OData can through an exception.
In our case, we have added Web Service DataSource and set this OData query for its Service Url:
If you see the query, it is selecting "ProductName1" property of "Product #1". But "ProductName1" property does not exist (correct property name is "ProductName"). When we use Postman for the OData query above, it shows an error which you can see from attached picture (ErrorWhenWeUsePostman.PNG, "Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'"). From the second picture (TelerikReportingGeneralError.PNG, "An error has occurred... Response status code does not indicate success: 400 (Bad Request).") you can see the result of our test report (in html5 report viewer) that has the same OData query.
The question is when we preview our report (in html5 report viewer) how can we show the error message that OData sent instead of showing Telerik reporting general error?
Instead of this message:
An error has occurred while processing Report 'TestReportWithWebServiceDataSource': Response status code does not indicate success: 400 (Bad Request).
This OData error message should be handled and shown on browser (html5 report viewer) when previewing report:
Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'
FYI: We are using Telerik Reporting version 22.214.171.124.
This is my post on Telerik forum related with this: How to get internal error message from Custom Report Resolver
I would like to request an HTML5 ASP.NET Core Report Viewer similar to the MVC version with wrappers. It would be great to be able to utilize Razor Syntax for developing instead of pure jQuery.
At the moment it's only possible to have your reports in old-fashioned projects.
It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).
We are using the external style sheet file (StyleSheet.xml) when designing our report from Web report designer. We want to see our style sheet applied on our report when we see the report from Web designer in design mode. In Preview mode it is working fine. But the problem here, it is not working in Design mode.
See the attached pictures. You find our problem on the picture ExternalStyleInWebDesigner-DesignMode.PNG
Is there any solution or a feature request needs to be created?
FYI: External style sheet is working in Standalone report designer in both design and preview mode.
Use only components from KendoUI for Angular. It would be understandable that such report viewer would provide less features, but it would remove dependency from jQuery and KendoUI for jQuery.
What's the long-term plan for supporting Linux and Telerik Reporting? The dotnet design team is looking to remove support for System.Drawing.Common on Linux platforms. They're recommending compiler warnings in .Net 6, and full PlatformNotSupportedExceptions in .Net7
When a report is saved in the Web Report Designer, a popup appears confirming that the report was successfully saved. However, it is visible for far too long and blocks users during this time.
This feature request is to add an 'ok', 'hide' or 'close' button to these types of popups so the user can dismiss it.
Make the Design-Time parameter values of the WebServiceDataSource editable through code.
Currently, the design-time values can be edited only by the report designers or by saving the report with the TRDX extension and editing the XML.
In the XML, to change the design-time values, you may edit the ParameterValues property which is a string.
Please add DropDownTree and/or TreeView as single- and multi-value parameter editors to accommodate Hierarchical data. It would be nice to have them out-of-the-box when available values come from a hierarchical/self-referencing table(s), but I would be happy if they could be integrated as Custom Parameter Editors. I was able to render and populate the dropdowntree with checkboxes, pass the correct selected values, but the 'Preview' button would never enable upon selection. Also, the dropdowntree's AutoClose(false) was not recognized. I know this can be achieved outside of the report viewer, but sometimes that method disrupts the layout and flow of the reporting view.
Add the ability to specify rounded corners for the border of TextBoxes, Pictures, Tables and all other similar controls.
Ability to split sections for use in Conditions and Formatting.
Example: Detail split into Detail-A and Detail-B where either or both may display based on a condition defined at the Section Split level.
For Crystal Report users (myself since 2008) this is a very important feature.
It allows a single report be used for detail or summary reporting as well as multiple conditions for display.
This is an example from CR:
Currently, when GroupFooterSection.PrintAtBottom is set to True, all subsequent sections will be moved to the next page. For that reason, the Report Footer also moves to another page even when its PrintAtBottom is True and both sections can fit on a single page.
If I set the Group Footer PrintAtBottom to False, it will be printed just below the Detail section, which may leave unwanted blank space between the Group Footer and the Report Footer.
I think that it is more intuitive to have both the Group Footer and the Report Footer printed at the bottom of the last page in this scenario, with the Group Footer just above the Report Footer.
I know it's a bit early to be asking for this, but I wanted to get a feature request on the backlog so it's trackable.
Currently, you already have a ReportViewer for WinUI3. This means you have a good head start for a ReportViewer that can be used in a .NET MAUI project and have native Windows support.
I'm mostly concerned about having support on a Mac, not the mobile platforms. So if you can build a MacCatalyst ReportViewer, you can cover a good portion of developers who are hoping MAUI can give them desktop support across platforms.
Tip: If you use SkiaSharp or Maui.Graphics for rendering, you can get automatic cross-platform support everywhere for free