Do you have the overview of the number of compile errors/warnings/to-dos and best practice errors in your customizations? Do you have the information broken down per team or even by module? Do you have an overview of the size of your customizations?

If you answered Yes to all the questions above read no further!

The heart beat of most development projects is the build. The more frequently the build is the more often you know the state of your project. If the build is broken you have a problem, you must hunt down! Preferably before breakfast!

A Dynamics AX project, however, can succeed without a single build, due to the rapid development features in MorphX. Eliminating the need for a build is both good and bad.

From a developer productivity view point it is awesome! There are no built-in coffee breaks interrupting the flow of development all day long. Ask any developer what he rather give up - the company car or the instant-run capabilities in AX. This may give you new insights into how you can spoil your developers in the future. 

From a management point of view it can become a nightmare. There is zero visibility into the state of the project. There could be compile errors all over the place - or even worse: Well hidden deep in a dark corner, where only your customers will venture.

In Dynamics AX 4.0 you can get visiblity into the state of the project; while maintaining developer productivity. Dynamics AX 4.0 can extract the state of the each element in the AOT and populate it in an Microsoft Excel spreadsheet.

 Here are the instructions:

  1. Download the attached Microsoft Excel spreadsheet. 
  2. Create rows in the spreadsheet to model your organization/team.
  3. Schedule a recurring execution of AX with a special startup command. (Preferably on a server in the basement - it will take hours to complete.)

Details are available on the Instructions page in the spreadsheet.