Core and reporting

[SBarnes]

In looking at needing to get reports from Jiwa into a .net core project as near as I can see the best way to do this and keep crystal in the mix would be to use the reporting service in the REST api and pull the output back as a pdf and display that.

Other than that the only other option is to use a third party reporting tool that will work with .net core which I would prefer not to do from a possible cost and learning curve issue.

Am I right in my assumption that the report service is the best option or am I missing something?

[Scott.Pearce]

In looking at needing to get reports from Jiwa into a .net core project as near as I can see the best way to do this and keep crystal in the mix would be to use the reporting service in the REST api and pull the output back as a pdf and display that.

Yes I would just get the .pdfs direct from our REST API route (GET /Reports/{ReportID}/PDF/Download). No crystal involved other than what comes with the REST API installation.

Other than that the only other option is to use a third party reporting tool that will work with .net core which I would prefer not to do from a possible cost and learning curve issue.

How would such a third party tool interface with Jiwa?

Am I right in my assumption that the report service is the best option or am I missing something?

What exactly do you mean by "Report Service"? The "GET /Reports/{ReportID}/PDF/Download" route? If so, then yes, that is the best option.

[SBarnes]

Yes, the class I believe is called Report Service in the Rest API

Third party tool directly accessing the database but can work in .net core Devexpress and Syncfusion both have options.