SSRS report architecture in AX 2012 R3

(4) Share

Report

Posted on by CU05031448-0

1,323

Dear team,

I go through about the architecture of SSRS report. Kindly validate pls .

[ End User Request]
↓
[ AX Client -- Form/Menu Item]
↓
[Controller Class]
↓
[Contract Class → Parameters]
↓
[RDP Class → Temp Table → Business Logic]
↓
[SSRS Report Server (.rdl)]
↓
[Rendered Report Output]

Am I correct?

Categories:

Microsoft Dynamics AX

I have the same question (0)

All responses (6)

Answers (2)

CU05031448-0 1,323 on at

Like (0)

Report
Copy link

Link copied!

Once available, pls validate my reply.

Was this reply helpful? Yes No
André Arnaud de Cal... 303,669 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

There is also an option to build an SSRS report based on a query instead of using a RDP class with a temporary table. What to use depends on the scenario. There are several blog posts available that explains how to build SSRS reports for AX 2012. What is the exact background of your question?

Was this reply helpful? Yes No
CU05031448-0 1,323 on at

Like (0)

Report
Copy link

Link copied!

Thanks Andre for the response.

I like to know about the flow in behind when the user running the SSRS report from the menu item.

There are two types of creating a report:

Query based

RDP based

Kindly validate for the RDP based report , is the above flow is correct?

Thanks

Was this reply helpful? Yes No
Verified answer

Navneeth Nagrajan 2,533 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi CU05031448-0,

For query based reports, the logic is you have data being fetched through a static query in the Application Object Explorer with a fixed set of fields and this defines the reporting dataset. This is usually used for reports where the data set is small. All the data displayed in the report through the fields is based on this static query. For example, HcmCourseDesign report.

For report data provider (RDP) based reports are based on a form or a menu item triggering the controller class. Now, this controller class will manage the execution by triggering the RDP class that contains the core business logic. The field data in the report is populated inside the RDP class. The X++ code required to populate the fields represented in the dataset that form the report is all built inside the RDP class. In addition to this, the controller class also is responsible for parameter handling that's defined in the data contract class There is an additional UI Builder class that is an optional component and is used for modifying the report parameter dialog window. All the data is later rendered in the .rdl file and this .rdl file is hosted in the SQL reporting services virtual directly. The report layout and design is managed through the report designer whose schema is managed inside the .rdl file.

Example, PurchPurchaseOrder or BankPaymAdviceVendV2 report.

In addition to these reports there is Ax Enum Provider dataset report that is used for building reports based on multi-selection of parameters. Example, AlertsetupReport. (References: https://community.dynamics.com/forums/thread/details/?threadid=b6a0ecb0-b55e-49d1-a5b1-7072d09073b8)

Hope this helps. Happy to answer questions, if any.

Was this reply helpful? Yes No
CU05031448-0 1,323 on at

Like (0)

Report
Copy link

Link copied!

Thanks Nagarjan,

As you mentioned, is the same concept used for D365F&O also ?

Kindly confirm pls.

Was this reply helpful? Yes No
Verified answer

Navneeth Nagrajan 2,533 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi CU05031448-0,

Yes, the same concept is used in D365 FO for SSRS Reporting. You can refer to the same.

References:

https://learn.microsoft.com/en-us/training/modules/build-reports-finance-operations/?source=recommendations

Was this reply helpful? Yes No