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:
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 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.
If you have any experience upgrading Dynamics AX code, we need your help to implement the right feature enhancements for the code upgrade toolset in Microsoft Dynamics AX.
Please spend 3-5 minutes on this short survey. Link to survey.
Your input is much appreciated.
In this ½ hour video Arthur Greef interviews me on the model driven development architecture of Dynamics AX. Small demos are shown during the interview including the powers of IntelliMorph and the layer technology.
Just now I've held my first sample of the Inside Dynamics AX 4.0 book in my own hands. Before the proud owner walked away with it again, I had a chance to photo the beauty!
If you want a copy for yourself, it is now available on Amazon.
If you already own a copy, make sure to review it on Amazon. I'm eager to hear what you think!
This week I'm visiting IDC - Microsoft's India Development Center located in Hyderabad - to conduct training on Dynamics AX development. Sitting on the back seat of a cab zig-zagging through the busy traffic in downtown Hyderabad I can't help thinking back on my very first Axapta (That was the product name back then) presentation. I did this presenation at DTB in London 1999, and it attracted 3 curious people wanting to learn about the intricacies of MorphX and X++. Now, a few years and thousands of miles later, I'm covering more-or-less the same material for a room packed with eager developers in India.
Traveling so far, and meeting with so many talented people, helped me understand something the many success-story memos and status reports couldn't. I'm left humble and deeply touched. Dynamics AX is on an amazing journey. And it is just getting started...
Last week a document on security considerations for Dynamics AX development was published.This 40 page document is a must-read for every X++ developer.
The document is available here:
Yurii Rasskazov has written a great blog on his experience setting up VSS with Dynamics AX. Here it is:
For more information on the version control system in Dynamics AX see the topics in the Microsoft Dynamics AX SDK under Microsoft Dynamics AX Programming Environment / MorphX Development Tools / Version Control System.
The solution is here!
The developer documentation for Dynamics AX has moved to a continuing publishing model. This means more and more documentation topics will be available as they are written, and not as previously only when a new version is released.
However, despite good intentions, the developer documentation released with Dynamics AX currently primarily contains the boiler-plate: "At the time of publication, no information was available for this topic." This even happens for topics that were documented in previous versions.
The documentation teams at Microsoft have work hard on verifying, proof reading and moving topics into the Html help. Only topics they have signed off are available in the Dynamics AX 4.0 RTM.
If you, like me, prefer less-accurate information to no-information, the solution is here.
Attached is an xpo-file, that when imported, will tweak the help system's behavior: If a help topic actually is available in the Html Help it will be displayed, just like the normal behavior. However, if a topic in Html Help just contains the boiler-plate message, then the legacy help system will take over, and display the topic from the legacy system.
This provides three benefits:
The downsides are:
[Update: The attached solution now also supports the 4.0 SP1 help][Update2: The attached solution now also supports incorrectly mapped topics ]
This post is provided "AS-IS" with no warranties, and confers no rights.