Finance | Project Operations, Human Resources, ...

when we exactly consider CONTROLLER CLASS in SSRS REPORT?

(0) Share

Report

Posted on by @rp@n

Hi All,

Can you please let me know when we exactly need CONTROLLER CLASS in SSRS REPORT?

As per my requirement i have to do one report for Purchase order. In dialog only we need to PURCH ID lookup.

As i know, i can achieve this requirement through ( CONTRACT + DP CLASS ).. Because i don't have any validation in dialog.

Is it correct?

Kindly let me know when we consider CONTROLLER CLASS in SSRS report?

Please give me more shed on this.

Thanks!

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Blue Wang Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @rp@n,

Controller class is used to control the report execution as well as preprocessing of the report data. The SSRS reporting framework uses this class to modify the report dialogs, calling the SQL Server reporting services, as well preprocessing parameters for the report.

Controller class is also used when reports are opened from a form and are needed to show selected record details.

Please refer this:www.dynamics101.com/.../

Was this reply helpful? Yes No
@rp@n 56 on at

Like (0)

Report
Copy link

Link copied!

Thanks

That i understand, but my question is "IS REQUIRED ALWAYS CONTROLLER CLASS?"

I saw in some customized and stand. reports using only CONTRACT + DP CLASS.

Please give me more shed on this.

Thanks!

Was this reply helpful? Yes No
Blue Wang Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @rp@n,

No, it's not necessary.

The specific class or combination depends on your needs.

You can even create reports without parameters, without using the contract class, and even without the controller class.

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report
Copy link

Link copied!

Yes, there is always a controller, as there is always a UI builder if you show a dialog. But if you don't need any special behavior, you simply use the default implementations and you don't even have to be aware of it.

Only when you need something custom, you create a specialization of the default controller.

Was this reply helpful? Yes No
@rp@n 56 on at

Like (0)

Report
Copy link

Link copied!

Thanks Martin,

Means if dialog is there in report as a parameter, then it will always required controller or UI Builder class. but depend on requirements.

if not , then we will go for contract + DP class .

is it rite?

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

Like (0)

Report
Copy link

Link copied!

No, that's not what I said. Let me make it even simpler:

1. There is always a controller. Period.

2. If you show a dialog, you're using a UI builder. The magic that builds the UI (the dialog) is the UI builder class. That's why it's called that way. If you're not building UI, then you don't need a UI builder, because there is nothing to build.

Was this reply helpful? Yes No