Finance | Project Operations, Human Resources, ...

Regular Tables in SSRS Reports in D365 F&O/Supply Chain - Any reason to use them?

(0) Share

Report

Posted on by AbominableDaxman

I am extending an SSRS report that is provided by our ISV partner as part of their ISV package. This report uses regular tables to store its data, instead of temporary tables. The report uses preprocessing to generate itself.

I am being forced to use regular tables from my report extension, because you cannot mix and match regular and temporary tables in an SSRS Report. This will generate an error.

I am wondering if there is any legitimate reason to still be using regular tables in an SSRS report, as opposed to temporary tables (either in-memory or temp db)? I may ask our ISV partner to change their report to temporary tables, but i wanted some information on whether it is appropriate to be using them under certain circumstances first.

Thanks,

Jonathan

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Martin Dráb 239,029 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I can't think of any good reason for using regular tables in pre-precessing data providers. They’re used for temporary data, and using actual temporary (TempDB) tables makes better sense, since this option was made available.

When checking when the support for TempDB was introduced (it was in AX 2012 R3), I found also a statement from Microsoft:

You should stop use the old SrsReportDataProviderPreProcess class but use the new base class instead for long running reports. You will see performance gain in case of multiple concurrent sessions on the same report.

Source: Improving SSRS Report Performance using new R3 features - Part 6.

Was this reply helpful? Yes No
AbominableDaxman 20 on at

Like (0)

Report
Copy link

Link copied!

Hi Martin-

As I was looking into this more, it seems that even Microsoft is not playing by the rules when it comes to the SalesQuotation.

When I look at SalesQuotationHeaderTmp and SalesQuotationDetailsTmp (both part of the ApplicationSuite package, and the temporary tables used by the out of the box SalesQuotation from Microsoft), those tables are regular tables also! Our ISV is extending those reports, and therefore it is Microsoft forcing us to use regular tables! Do other see the same thing in their environments?

It is my understanding that one cannot extend a report to use temporary tables if there are already regular tables being used in the report. So by using regular tables for this report, Microsoft is forcing developers to continue doing this for extensions to the report as well. Might the use of regular tables for this report have something to do with future traceability and reprintability of previously generated Sales Quotations?

Thanks,

Jonathan

Was this reply helpful? Yes No
Martin Dráb 239,029 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

What kind type of tables you can use isn't driven by what tables are used there, but what kind of data provider it is. SalesQuotationConfirmationDP extends SrsReportDataProviderPreProcess, and SrsReportDataProviderPreProcess uses regular tables.

I think the only reason is that it was written long before SrsReportDataProviderPreProcessTempDB was introduced and there wasn't a strong enough reason to rework it (and force customers and partners to change their customizations as well).

Was this reply helpful? Yes No