Quantcast
Channel: Microsoft Dynamics AX Forum - Recent Threads
Viewing all articles
Browse latest Browse all 72043

AX 2012 - Visual Studio Reporting Objects Purpose and Organization

$
0
0

Hi,

I'm new to the forum and to Dynamics AX 2012 report development, and have a question around the structure of the objects created for reporting, and the best practices for organizing them.

Visual Studio Solution

I'm trying to understand the purpose of the Solution.  I get that it's a container that holds projects, and that you can save it to disk.  It doesn't appear you ever deploy it to the AOT or SSRS or anything like that.

- Do you create 1 solution per project?  Or group multiple projects into a single solution?  Or is the solution only used for the purposes of holding the project as you develop it prior to deploying to AOT, and it doesn't really matter?

- Should we all save all of the solutions we build to disk?  Does it even matter, since it seems that once we deploy a project to the AOT, it can always be re-added to a new solution later?  Is the solution transient?

Project

- Should each project only contain 1 report?  Or should we group similar reports (for example, sales reports) into a single project?

Report

- Should each report only contain 1 design?  Or should we have multiple designs in a single report if they're just different ways of displaying data from the same data set?

I appreciate any guidance you experts can provide.

Thanks!

Tony


Viewing all articles
Browse latest Browse all 72043

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>