Service Pack 2 for Dynamics AX 4.0 – Released
It is now available on PartnerSource. Unlike SP1, it is not a whole new install, and requires an existing AX4.0SP1 installation. (That is the only upgrade scenario available.)
Overview
Microsoft Dynamics AX 4.0 Service Pack 2 includes:
~Support for 15 different document AXDs in the Application Integration Framework.
~Updates and bug fixes to functionality shipped in Microsoft Dynamics AX 4.0 Service Pack 1. Changes include areas such as Financials, BI & Reporting, Client, Cost Accounting, Customer Relationship Management, Developer & Partner Productivity Tools, Enterprise Portal, Inventory Management, Manufacturing, Master Resource Planning, Product Builder, Project Accounting, Application Object Server, and Shop Floor Control.
~Several fixes focused on stabilizing the Client and Application Object Server. This was a main focus for SP2.
Technorati Tags: Dynamics AX, Axapta Source, Axapta, Microsoft, ERP, MBS


Comments(3)

Quite impressive list – as usual with Axapta service packs
. And perfect timing – just starting new customer implementations (actually two customers).
I agree – glad I noticed it so quickly as I too am working on a couple of implementations myself as well.
Recent blog post about testing:
http://blogs.msdn.com/micahel/archive/2007/08/01/Quantum-Testing.aspx
Acutaly not directly related to Axapta as such, but made me considering my life
I’m just curious how others do development and testing when creating new implementation for new customer?
Which scenario is the case most times:
1) “Extreme programming” – project team of 1,2 or 3 (at most) professionals rapidly create and deploy all the things necessary. Usualy ends on “Best effort” project.
2) “Bureaucratic” project – a lot of peaple, a lot of paperwork, slow developments and deployment. Big to very big budgets.
3) “Don’t care” projets – customer left on ist own (almost). Very slow and very vital new developments.
Also separate question and story is how service packs are applied.