Currently, any custom implementations of the IResourceResolver and ISharedDataSourceResolver require using a parameterless constructor because the types are initialized via Reflection at runtime.

We would like to be able to dependency inject services into the custom resolver implementations through the constructors.

                <Telerik.ReportViewer.BlazorNative.ReportViewer
                    @ref="reportViewer"
                    ServiceType="ReportViewerServiceType.REST"
                    PageMode="PageMode.SinglePage"
                    ServiceUrl="@(ServiceUrl)"
                    @bind-ReportSource="@ReportSource"
                    AuthenticationToken="@(AuthToken)"
                    ScaleMode="(ScaleMode)ReportSetItem.Report.ScaleMode"
                    @bind-ParametersAreaVisible="@ParametersAreaVisible"
                    Scale="1.5">
                </Telerik.ReportViewer.BlazorNative.ReportViewer>

The variable, ParametersAreaVisible, is set to false. The report viewer is still showing the parameters area. I went back to the designer and set all parameters to Visible = false. When I did this, the parameters area is not displayed.

The report viewer should respect what is bound to ParametersAreaVisible.

Using the MySQL Connector/NET data provider with the latest version of Telerik Reporting - Telerik Reporting - Progress® Telerik® Reporting 2024 Q3 (18.2.24.924), leads to the following error when using Stored Procedures:

System.ArgumentException: Object of type 'MySql.Data.MySqlClient.MySqlCommand' cannot be converted to type 'System.Data.SqlClient.SqlCommand'.
   at System.RuntimeType.TryChangeType(Object value, Binder binder, CultureInfo culture, Boolean needsSpecialCast)
   at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig)
   at System.Reflection.RuntimeMethodInfo.InvokeArgumentsCheck(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Telerik.Reporting.Processing.Data.SqlProviderFactory.DeriveParameters(IDbCommand command)
   at Telerik.Reporting.Processing.Data.SqlCommandProvider.ResolveProcedure(IDbCommand command, SqlDataSourceParameterCollection parameters)
   at Telerik.Reporting.Processing.Data.SqlQueryProvider.CreateCommandCore(IDbConnection connection, Boolean evaluateParameters)
   at Telerik.Reporting.Processing.Data.SqlQueryProvider.CreateCommand(IDbConnection connection)
   at Telerik.Reporting.Processing.Data.SqlDataEnumerable.<GetEnumerator>d__2.MoveNext()
   at Telerik.Reporting.Processing.Data.LazyList`1.LazyListEnumerator.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at Telerik.Reporting.Processing.Data.SeedDataAdapter.Execute(IEnumerable`1 data)
   at Telerik.Reporting.Processing.Data.ResultSetAdapter.Execute(IEnumerable`1 data)
   at Telerik.Reporting.Processing.Data.MultidimentionalDataProvider.Execute(MultidimensionalQuery query)
   at Telerik.Reporting.Processing.DataItemResolveDataAlgorithm.GetDataCore(IDataSource dataSource, MultidimensionalQuery query, IServiceProvider serviceProvider, EvalObject expressionContext, IProcessingContext processingContext)
   at Telerik.Reporting.Processing.Report.GetDataCore(IDataSource dataSource, MultidimensionalQuery query)
   at Telerik.Reporting.Processing.DataItemResolveDataAlgorithm.ResolveData(String processingId, InMemoryState inMemoryState, MultidimensionalQuery query, Func`1 getDataCore, EvalObject expressionContext)
   at Telerik.Reporting.Processing.Report.ResolveData()
   at Telerik.Reporting.Processing.Report.ProcessItemCore()
   at Telerik.Reporting.Processing.Report.ProcessItem()
   at Telerik.Reporting.Processing.ReportItemBase.ProcessElement()
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)

The previous version - Telerik Reporting - Progress® Telerik® Reporting 2024 Q3 (18.2.24.806), is working fine.

If I render a report that includes a HtmlTextBox item with line breaks in its value(<br />) to PDF with the Skia graphics engine and a font such as DejaVu Sans, the <br /> tags are rendered as squares.

Sample HTML:

<p>line1<br />line2<br /><i>line3</i></p>

Using a font such as Arial, there are no such issues. However, before 2024 Q4, it wasn't a problem when using the DejaVu Sans font as well.

I often need to have the same Report Parameters in different reports, including the main and its subreport. Currently, I need to add the parameters manually.

It would be very useful if we could copy/paste Report Parameters between reports.

I have a use case which requires me to record data whenever a report is printed. In pursuit of this, I am trying to replace the build in Print() tool and replace it with my own.

I have read this documentation which shows how to remove and reorder the buttons well enough, but it does not support adding a new tool all-together. Javascript event listeners will not work for me because ultimately what I want to do is accomplish a database write, which would be insecure through javascript.

 I have been able to establish a workaround by following this documentation and creating a button *outside* of the ReportViewer, however, I would still like to find a way to put the button inside of the ReportViewer toolbar if possible. 

When the WinForms Report Viewer is initialized from within the Form.Load Event, and the RefreshReport() method of the viewer is invoked before it is added to a parent form, the following exception will be thrown: 

Telerik.ReportViewer.WinForms.Licensing.UiLicensePresenter.ShowWatermark(Action showWatermarkCallback)
   at Telerik.ReportViewer.Common.TelerikLicensePresenterBase.PresentWatermark(Action showWatermarkCallback)
   at Telerik.ReportViewer.WinForms.WinViewer.OnPaint(PaintEventArgs eventArgs)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lpa

Graph markers, it would be nice to have a few more marker types for the chart, I would really like a up and down arrow, or a reversed triangle. also a left and right arrow/ triangle, and how about a star?

Hello,
I already developed in the past with your WPF controls and I'm mostly very happy. The controls are nice and the programming model (MVVM) is well done. I always recommend your controls the all my friends developer out there.
For a new project, I'm evaluation the Report Design + Viewer and I must say I'm very disappointed by the all product. 
First the general looking and feel seems coming from an old Visual Basic 6 age with outdated button toolbar + gui; non sizable dialogues like the one to choose fields (attached) With data source coming from entity model, the field and navigation property are often long and this is painful and useless to scroll horizontally to see the field name.
Coming back to data source, the report wizard is also confusing asking for an data source name rather than asking for an existing connectionstring and then create a new one for your need internally if needed. Also, the experience with an existing data model object is poor because the Data Member question is not obvious and when I select one the entity table, the wizard prompt with an alert see capture attached. If I don’t select any member, no alert but the field list is useless because I don’t see any field (see capture).
In conclusion, it seems to me the Report components are not done by the same team or at least are not develop in the same spirit and quality than the other controls.
I hope you will bring us a brand new controls asap.
Thanks for reading me 
Best regards
-Vince

Telerik.reportdesigner.exe crash with Null reference exception when add new object datasource with "Choose a data source member".

In the attached photo, I combined the first 2 pages of the PDF I get when I export the reports as a PDF (there were 198 pages in total). The second page is the continuation of the bar chart, as the bars expand. This is not readable or insightful to a user who wants to view the report, as he/she can not see any of the labeling of the X or Y axis on the second page. I would like to see labeling of both the X and Y axis on each page, so that the reports are easier to read. The same applies for graphs, columns, and table reports as well. 

It's confusing which rule does what by looking at the current UI...would be nice to give them aliases\friendly names which mean something when you go back 2 months later, know what I mean?

I've been using the Stand Alone Report Designer a fair bit lately but find myself having to switch between the Home, Insert and Data tabs quite a bit. It would be a great time saver if the Report Designer had a dockable toolbar (defaulted to the right) like in Visual Studio with short-cuts to adding things like Text boxes, pictures, etc.

Regards

Edu

Presently, when you use the Fields property, you can only access simple type properties : "= Fields.CompanyName", "= Fields.CompanyPhone". The complexe types are not accessibles via the Fields property. If you want to print a complexe type property, you need to use the expression "= ReportItem.DataObject.Company.Name", "= ReportItem.DataObject.Company.Phone".

In my opinion, this is not very intuitive. 2 differents ways to read a property depending of his type! It would be great to be able to access anything from the Fields property.