My project uses the following two dependencies:

• Telerik.UI.for.Blazor (v9.1.0)
• Telerik.ReportViewer.BlazorNative (v19.1.25.716)

However, when I build my application and navigate to the page of the Native Blazor report viewer, the following error is thrown:

“Telerik.Blazor.Components.TelerikWindow does not have a property matching the name ‘Centered’.” at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.ThrowForUnknownIncomingParameterName(Type targetType, String parameterName) at Microsoft.AspNetCore.Components.Reflection.ComponentProperties.SetProperties(ParameterView& parameters, Object target) at Microsoft.AspNetCore.Components.ParameterView.SetParameterProperties(Object target) at Microsoft.AspNetCore.Components.ComponentBase.SetParametersAsync(ParameterView parameters) at Telerik.Blazor.Components.TelerikWindow.SetParametersAsync(ParameterView parameters) at Microsoft.AspNetCore.Components.Rendering.ComponentState.SupplyCombinedParameters(ParameterView directAndCascadingParameters)

Service Stack 4 support, specifically to integrate reports into sitefinity

Option 2 is a github os provider we can use perhaps...

Actually, the report footer displays right after the preceding content. It would be very useful to force it to the bottom of the page, just before page footer

It would be useful to have tooltips to table header columns so we can explain what each column is showing.

Having the ability to have a line/box to force a new page mid way through a section would be much more useful than making use make new groups to use one as it just makes everything more difficult

As HtmlTextBox item supports only a limited number of HTML tags and CSS attributes, it cannot be used for rendering a richly-formatted text. The solution can be to use a WebBrowser control (https://msdn.microsoft.com/en-us/library/system.windows.forms.webbrowser.aspx) in a user function to render HTML to a bitmap and display it in a PictureBox item as described in this KB article: http://www.telerik.com/support/kb/reporting/details/how-to-render-any-html-tags-in-reports

Let us know if you think providing such functionality out-of-the-box would be beneficial for your reports.

Leave here a comment with your thoughts on this subject or vote for this feature.

Currently, NoDataMessage property is available for Table/List/Crosstab, Graph and Map items only (http://docs.telerik.com/reporting/report-structure-dataitem-set-no-data-message)

Providing NoDataMessage property for reports as well will simplify the approach to display the message in case no data is returned from report's data source.

Please consider adding an RTF Text Box control to your report toolbar.   Crystal reports has this ability which we've used on many of our reports.  Currently the only work around for changing the RTF data to something that Telerik Reports will print cleanly, is to create a user defined custom function.

Problem description:
On ".net Framework" it is a supported scenario that assemblies with datasources and/or functions are loaded into the standalone ReportDesigner. This assemblies are used while designing and later also in the ReportViewer while executing the report. Feature described here https://docs.telerik.com/reporting/standalone-report-designer-extending-configuration

Now that .net 6 is release by MS the same feature is needed there. The problem is that the "standalone ReportDesigner" is targeting ."net framework" which means it can only load assemblies targeting ".net framework" or up to ".net standard 2.0". But that is not sufficient because on ".net standard 2.0" only EntityFrameworkCore3.1 is supported and all newer version (EF Core 6.0) are not.  See here https://docs.telerik.com/reporting/knowledge-base/use-reporting-in-dotnetcore-with-entity-framework-core

So in summary:
It`s not possible to use EF Core 6.0 (and upwards) DataSources in the given "standalone ReportDesigner" because it is targeting .net framework. It`s critical to be able to use the newest EF Core versions as DataSource to not be blocked from upgrading a ".net framework" application to .net 6 where the described feature/scenario is used. I need to use the "standalone ReportDesigner" because it gets shipped with the application to edit the reports individually by the enduser. The "VS ReportDesinger" is going to get the upgrade but this would only be usable as a developer before shipping the application.

Feature request:
Upgrade the "standalone ReportDesigner" to target .net 6.

Hi Team,

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.

Thank you,

Patrick

Tip: If you use SkiaSharp or Maui.Graphics for rendering, you can get automatic cross-platform support everywhere for free

Some reports contain a lot of detail (audit reports, sales reports).  Users need to quickly find transaction numbers, etc. when balancing financials.  

I need to be able to have page breaks inside a Telerik reporting Table based on my row groups.  Forum posts indicate that this is not currently possible.  Thank you. 

Implementing Drag&Drop for the Web Report Design is a major step toward feature parity with the Standalone Designer, and helps end-users leverage their established workflow when migrating to the Web Report Designer.

1. Dragging a field from the Fields list onto the surface should A) Create a default Textbox. B) Populate that Textbox with a simple =Fields.field expression.
   
2. Dragging and dropping a component from the component tree should create that component at the drop location.

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.