Organizing a Reporting Framework

[Mike]

Hello,

I want to use Reporting for a series of reports for my organization - the site is based in DotNetNuke. 

I've used reporting before and am reasonably comfortable with it all... but I'm curious if anyone has any suggestions for broadly how to organize the reports. I would like to make a central library of reports and a report controller of sorts that handles permissions, access, and parameters. Then, I'll probably make a DNN module that shows reports matching some set of conditions. 

But, before I dive in with this, I'm wondering if anybody has any suggestions or thoughts on how to organize and handle many reports. What's the best way to make sure that individual reports get the right parameters? What's the best way to store a list of reports and parameters? Are there any features of functions of Telerik's framework that apply specially in this sort of context?

Thanks,

Mike

[Stef]

Hi Mike,

Take a look at our Best Practices help article. Also check the solution structure of our local demos located by default under C:\Program Files (x86)\Telerik\Reporting <version>\Examples and the ReportManager object used to gather information about the existing report definitions in the assembly.

It is recommended to use report parameters mainly to control the data and/or the reports layout. Try to avoid using a lot of parameters per report, thus maintenance will be eased. Parameters values can be passed by iterating through the report instance ReportParameters collection.

I hope this points you into the right direction.

Regards,
Stef
Telerik

[James]

The Best Practices help article link is broken. http://www.telerik.com/help/reporting/best-practices-solution-structure.html

[Dimitar]

Indeed, that article has been archived. I would recommend checking the following blog posts instead:

• Best Practices for Data Retrieval in Telerik Reporting
• Next Level Report Engine Explained (telerik.com)