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. 

Hi,

Have the possibility to have the "Select Case" or "Switch" function in the expressions.

Thanks!

The Telerik.Reporting.Report class has the property ExternalStyleSheets which is an ExternalStyleSheetCollection.

This collection consists of objects of the type ExternalStylesheet which has private Name and ResourceKind properties.

Would be great and make sense to make these properties public since that would help when the external stylesheets need to be resolved dynamically, though a custom IReportSourceResolver for example.

We separated our data objects into a library project and then referenced it via the web.config. It works as intended, both in the designer and during data retrieval, but to update the dll with more objects we have to restart the whole site.

It would be very useful if we could substitute our assemblies without restarting the website.

Hi

I need to adjust line spacing in multiple line textbox but currently there seems to be no way to do that. Please add this feature!

Thanks

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).

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

Sources:

designs/system-drawing-win-only.md at main · dotnet/designs (github.com)

Breaking change: System.Drawing.Common only supported on Windows - .NET | Microsoft Docs

We can use Telerik UI components with gRPC service however, Telerik reporting service and HTML 5 viewer do not support gRPC.

With gRPC use growing among the developers, we would like to see Telerik reporting support gRPC out of the box.

We have many reports that contain grids using Table controls. We are using the HTML Report Viewer with the enableAccessibility option set to “true” to display these reports to application users. 

Using this configuration, the report when run in a browser generates markup using absolutely positioned DIVs instead of TABLE tags for the grids in the report. The accessibility company provided documentation that the generated report content is in violation of WCAG 2.1 A, 4.1.2, Name Value Role since the generated report content is neither a semantic HTML table nor adheres to the ARIA table pattern. 

Since Reporting Tables are rendered as DIV elements, you need to ensure they implement the following ARIA Design Pattern specifications:

• The table container needs role="table".
• Each row container needs role="row" and to be either a DOM descendant of or owned by the table element or an element with role="rowgroup".
• Each cell must be either a DOM descendant of or owned by a row element and to have one of the following roles: 
  • columnheader if the cell contains a title or header information for the column.
  • rowheader if the cell contains the title or header information for the row.
  • cell if the cell does not contain column or row header information.
• Remove the aria-label from each cell. Following this design pattern, only the element with role="table" should have an aria-label or aria-labelledby value to provide an accessible name.
• If there is an element in the user interface that serves as a label for the table, the table element needs an aria-labelledby property with the value as the ID of the labeling element. Otherwise, a label must be specified for the table element using aria-label.
• If the table has a caption or description, the table element needs an aria-describedby property with the value as the ID of the element containing the description.
• After these remediations, it should no longer be necessary for the cells to be focusable unless they have an interactive function. Removing the tabindex from the cells will also reduce the number of unnecessary tab stops.

Add the "Not In" operator for the Filter rules - Filter Rules - Telerik Reporting.

Currently, when I create a report with the Standalone Designer and localize it, I can preview it only with the language of the machine where I run the designer.

It would be very helpful to have the option to select one of the languages I have set up during localization when previewing.

It would be great if you could introduce the ability to create custom reusable color palettes in Telerik Report Designer, so I don't have to declare the same set of colors for each chart I need them.

If you have a lot of graphs in your report then it is more convenient to change the color palette one place.

Currently, the fields' names are case-sensitive for those 2 data sources while other data sources, like the CSV for example, will ignore the casing.

For example, if there is a JsonDataSource with a Column1 field, it has to be written exactly as is in the expression while in the CsvDataSource, the field will be resolved even when written like Fields.column1 in an expression.

Enable retaining editable textboxes when Exporting to PDF.

For example a PDF Re-order form with editable textboxes for order Quantity so the user can enter order Quantities.

Our clients enter information using the radeditor and in many cases want to embedded tables and graphics into their text.  Using your reporting tool there is no way to print this information.  I know you have suggested using your table and image tools, but that doesn't work when you are dealing with freely formatted text so the existance and location of the tables and images cannot be predicted.

We are using Telerik reporting R2.2022 version in our project. Some of our reports have html link (created with tag “a”). If we preview those reports html link doesn’t act as an actual hyperlink, so it’s not clickable. We know that there is a HtmlTextBox limitation not to be interactive in WinUI report viewer. But this is important for us to be able to click on html link on WinUI and we need that functionality.  

I tested WinUI example project (CSharp.WinUIExample.VS2022.sln) and opened SwissQRBill.trdp report. The report has some links to the external source in internet, which is not clickable, but if you open it in Standalone report designer it’s clickable.  

Is it on your roadmap to implement that feature? 

Thanks,

Currently, the WinUI ReportViewer has a hard dependency on Windows due to the fact that the internals rely on the Win32 print dialog.

This means I cannot define the ReportViewer in a WinUI class library to be shared with multiple front-end WinUI projects. If you attempt to do this, there's an internal crash because the project cannot resolve  System.Windows.Forms.

This feature request is ask if you can replace the Win32 print dialog with the WinRT printing API. 

Research Note:  Here's a GitHub thread where Microsoft is discussing the topic Question: Printing in WinUI 3 Desktop · Issue #4419 · microsoft/microsoft-ui-xaml (github.com). Here's their current recommendation:

var hWnd = WinRT.Interop.WindowNative.GetWindowHandle(App.StartupWindow);
var printMan = PrintManagerInterop.GetForWindow(hWnd);

await PrintManagerInterop.ShowPrintUIForWindowAsync(hWnd)