Report Designer ASP.net Core Datasources

[Yoab Youssoufou]

Hello, I've been able to reproduce your report designer in asp.net core, When it is time to add a dataset, the only option I have is to select a SQL dataset for SQLServer, I am using a PostgreSQL database for this project, how can I create a PostgreSQL dataset? attached is my interfcae. 

Attachment: reportdesigner_90509184.7z

[Vinoth Srinivasan]

Hi Yoab, 

 

Thanks for your interest in Syncfusion components. 

 

We have SQL datasource only in ASP.NET Core Report Designer application, but we can able to connect the custom datasource using external data extensions like custom data extension. We have prepared ASP.NET Core Report Designer sample with PostGreSql datasource option and it can be downloaded from below location. 

Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/ReportSample_core1369628835.zip 

 

We have prepared ASP.NET Core PostGreSql datasource extension sample and it can be downloaded from below location. 

Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/DataExtensions.PostgreSQL-1962018928.zip 

 

Please find the below steps to add the PostGreSql DataExtension sample in our WebReportDesigner sample. 

 

Step1: Add the PostGreSql Extension project reference to our Web ReportDesigner sample as shown in below snap: 

 

   

 

Step2: Add the Configuration section in AppConfig file as shown in below code example. 

 

App.config 

<?xml version="1.0" encoding="utf-8"?> 

<configuration> 

  <configSections> 

    <section name="ReportingExtensions" type="Syncfusion.Reporting.Extensions.Configuration.Extensions, Syncfusion.Reporting.Web" allowLocation="true" allowDefinition="Everywhere" /> 

  </configSections> 

 

  <ReportingExtensions> 

    <DataExtension> 

      <Extension Name="PostgreSQL" Assembly="Syncfusion.Reporting.DataExtensions.PostgreSQL" Type="Syncfusion.Reporting.DataExtensions.PostgreSQL.PostgreSQLDataExtension"/> 

    </DataExtension> 

  </ReportingExtensions> 

</configuration> 

 

 

Step3: Add ReportDataExtensions in Report Designer control as shown in below code example. 

 

Please find the below step how to specify the PostGreSql in ASP.NET Core Report Designer application using ViewBag. 

 

Index.cshtml: 

<sf-report-designer id="reportdesigner1" create="controlInitialized" service-url="../Home" report-data-extensions="@ViewBag.ReportDataExtensions"> 

 

</sf-report-designer> 

<sf-script-manager></sf-script-manager> 

 

 

HomeController.cs: 

  public ActionResult Index() 

        { 

            ViewBag.ReportDataExtensions = new List<ReportDataExtensionsModule>(); 

            var ReportDataExtension = new ReportDataExtensionsModule(); 

            ReportDataExtension.Name = "PostgreSQL"; 

            ReportDataExtension.ClassName = "PSQLDataSource"; 

            ReportDataExtension.ImageClass = "e-reportdesigner-datasource-psql"; 

            ReportDataExtension.DisplayName = "PostgreSQL"; 

            ViewBag.ReportDataExtensions.Add(ReportDataExtension); 

            return View();        } 

 

 

Output snap: 

 

 

 

Regards, 

Vinoth S. 

[Yoab Youssoufou]

Thank you for this example, but please I have tried all sorts of connection strign and keep getting an error. I ran your example and entered connection string as shown in attachment with or without authentication I keep getting samne error. This is the connection string that works fine in my ASP.net Core wepplication

Attachment: PostgresConnectionString_efcf7799.7z

[Vinoth Srinivasan]

Hi Yoab, 

Thanks for your update. 

If you are passing the username and password within connectionstring then, could you please choose the Authentication type as None as shown in below snap. 

 

Else if you are specifying connectionstring without username and password then choose the Authentication type as Authentication and pass the username and password as shown in below snap. 

 

Regards, 

Vinoth S. 

[Yoab Youssoufou]

Hello,

Thanks It's fine now

[Mahendran Shanmugam]

Hi Yoab, 

Thanks for your update. 

We were happy to hear from you the issue was resolved. 

Regards, 

Mahendran S.