Microsoft Dynamics AX 2012 is here!

Today we announced the public availability of Microsoft Dynamics AX 2012.

Microsoft Dynamics AX 2012: Powerfully simple

Microsoft Dynamics AX 2012 empowers people to anticipate and embrace change, enabling businesses to thrive.


A powerful foundation that is purpose-built for five industries: manufacturing, distribution, retail, services, and public sector, along with comprehensive, core ERP functionality for financial, human resources and operations management. All packaged in a single global solution thus giving customers a rapid time to value.


Agility through a set of unified natural models that serve as a library of business processes reflecting real-world situations. This enables customers to easily modify their organizations and processes to meet their changing business needs.


Simplicity through an easy-to-use solution offering access to information that is relevant to the work at hand. The familiar Microsoft Office user interface drives adoption and the enhanced business intelligence (BI) capabilities help customers uncover fresh insights that can lead to faster and more informed decision making.

For more information see:

Comments (2)

  1. I believe you might be impressed when you take AX 2012 for a spin. The end-user experience is beyond comparison with previous releases, and the developer tool set is much improved – including the documentation. By the way – You don't need to wait you can try it out today.

  2. nobloat says:

    The previous versions were anything but simple. Form upon form, upon form, with hundreds of buttons and grids that mapped directly to the database. The user almost needed to have a grasp of the database schema to make some sense of what he/she is doing.

    From a programmers' point of view, things are even worse. State and logic scattered between tables and classes (encapsulation? are you joking?), cryptic class and method names (FormLetter ?!), no code comments, denormalized database schema, redundant information, tables with no primary keys(!), wrong design pattern implementations and a dreadful development environment.

    So Microsoft needs to have implemented everything from scratch (and consequently ditched it's partners' code base) in order to be able to support the above claims. Let's wait and see…

Skip to main content