What are the limitations in Syncfusion ASP.NET Core ReportViewer?
At present Syncfusion ASP.NET Core ReportViewer has following limitations when compared to other web platforms like JavaScript, ASP.NET WebForms, ASP.NET MVC.
Features | Comments |
Chart, Gauge and Maps Report Items export | Report Viewer will generate the export document from server and mentioned report items are converted as image using WPF platform components for export. But WPF platform cannot used with ASP.NET Core hence we are working from our side to check the possibilities to include this feature support with ASP.NET Core application which has a combination of .NET Framework. |
Image Report Item | With the current implementations, we are providing the image to client side by changing the image data with respective format of image. We are getting the problem to achieve the same with ASP.NET Core. We are working to providing the image item support with alternative way. |
Data Source support | As of now, we have completed the data source support only for the SQL Server. We planned to add the additional data source support based on the support available in .NET Core platform Based on following article, we will not have the support for OLEDB. https://blogs.msdn.microsoft.com/dotnet/2016/11/09/net-core-data-access/
OBDC – We have a doubt to include based on comments available in the above article. Need to have further analysis to add this data source support based on further analysis. |
HTML, PPT | We have completed the supporting changes for Excel, Word and PDF. We need to work for other exporting supports HTML and PPT Exports. |
SSRS feature support | We only support SQL 2017 Reporting services API in ASP.NET Core Report Viewer. The lower version of SSRS will not work in ASP.NET Core Report Viewer. |
HTML Support | We have not integrated the HTML Text support with ASP.NET Core Report Viewer due to the compatibility of current implementation. |
Map Report Item | We have not integrated the map Report Item with ASP.NET Core Report Viewer due to the compatibility of current implementation. |