Geeks With Blogs
Satya Srikant Mantha Reflecting DAX NET and SQL Server

A Reporting project consists of a set of assemblies used to create SQL Server Reporting Services (SSRS) reports which can be used in Microsoft Dynamics AX.  This project is created in Visual Studio and has two templates : C# and VB.NET.

A typical layout of the solution file created is shown below:

Dynamics AX reporting project layout

Project Element File Extension Description
Solution File *.sln Contains one or more reporting projects.
Reporting Project *.dynamicsproj Contains necessary files and assemblies to create a report.
Model File *.moxl Contains a model for the reports, each report should have a top level reporting element.
Business Logic Project *.csproj, *.vbproj Contains the Business logic for the reports. You can create a data method that defines or modifies data that displays in a report. The code for the report method is stored within a code file contained in the business logic project. The programming language that you use to write the code depends upon the type of reporting project that you are working in: Visual C# or Visual Basic.
Code File *.cs, *.vb Contains code for the reports in a model.

Label resource file

*.resx

Contains localized resources in a standard .NET resource file.

 

Project Assembly and Reference

You can add assembly reference to a reporting project. A project reference can be added which is a reference to another reporting project or a business logic project within the same solution.

Important: It is recommended that you use a project reference rather than an assembly reference when adding a reference to another reporting project. This allows the referenced reporting project to be included in the package that is created when the importing reporting project into Microsoft Dynamics AX. In addition, you need to be careful when adding an assembly reference in a nested business logic project. The reference must be able to be resolved after the reporting project is packaged and imported into Microsoft Dynamics AX, and then later unpackaged.

Project Output

When you build a reporting project, assemblies with file name extensions *.Model.dll and *.BusinessLogic.dll are created and placed in the location specified as the output path for the project. In addition, *.pdb files may also be created during the build process.

If translated resource files exist, satellite assemblies with the .Model.resources filename extension are created.

Posted on Monday, March 9, 2009 10:43 AM Enterprise Portal Reporting | Back to top


Comments on this post: Reporting Services for Microsoft Dynamics 2009 Enterprise Portal – Part 2 Reporting Projects

# re: Reporting Services for Microsoft Dynamics 2009 Enterprise Portal – Part 2 Reporting Projects
Requesting Gravatar...
I’m building reports atop of a Dynamics AX data-provider. And so my solution doesn’t contain an RDL file… it contains a “.dynamicsproj” file. What i am looking for is a simple way to create Reports from an existing “generic” Report.
Maybe in the same matter as described by this link:
http://stevestedman.com/2012/03/using-your-own-rdl-as-a-ssrs-template/#comment-193

In a nutshell: i have 1 complex "dynamicsproj" file and wish to use this as a Template for creating other Reports. All for Dynamics. So there is no RDL file and no Code-behind.
Any and all help is welcome.

Many Thanks
Left by Heinrich on Oct 09, 2012 12:57 AM

Your comment:
 (will show your gravatar)


Copyright © ssmantha | Powered by: GeeksWithBlogs.net