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:
Details are available on the Instructions page in the spreadsheet.
I've just uploaded my first AX screencast to Channel9. It is a 20 minute video with a demo of the Unit Test Framework in Dynamics AX.
Here is the link:
Over the coming months I plan to create more screencasts on general development topics in Dynamics AX. If there are any specific topics you would like a screencast to cover, please let me know.
Feedback, please! If you have any comments to this screencast, please add a comment to this blog post. I would really like to know if you find this screencast useful. (or not).
I'm a member of the new team called the Microsoft Dynamics AX Partner Productivity team, which is part of the Microsoft Dynamics AX product development organization. Our charter is to provide tools and content to empower partners to complete more implementations with their existing resources. Our goal is to understand your key pain points during an implementation and we have created a survey to collect your feedback to help us prioritize projects planned for upcoming releases.
Here is a link to the survey:
We request feedback from all disciplines involved in a Microsoft Dynamics AX implementation: Pre-Sales, Project Management, Consulting, Development and Testing. Please forward this to the appropriate people in your organization so we can get a complete picture of your implementation cycle.
You can also review implementation tools already available at our landing page on the MBS PartnerSource portal at https://mbs.microsoft.com/partnersource/products/axapta/partnerproductivity
We hope you will also engage with us at the Microsoft Convergence 2006 EMEA in Munich, Germany. Look for the Partner Productivity team at Microsoft Dynamics AX Expo booths as well as roundtable sessions during the conference in November. Register for Convergence at https://www.microsoft.com/europe/convergence
Thanks you sincerely for your participation,
Microsoft Dynamics AX Partner Productivity team
Do you want to be a member of team dedicated to make life easier for AX partners? My team is full of energetic and highly skilled team members with a desire to deliver tools and content enabling partners to smoothly and succesfully implement AX. Being a member of the Partner Productivity team enables you to:
We have 3 open positions: