Pages

Tuesday, 11 February 2014

What is new in AX 2012


·         EDT relations have been moved to table level.
·         The UnitOfWork class to simplify database transaction management.
·         Inheritance among tables, similar to class inheritance.
·         Full text index support to quickly query words that are embedded in the middle of a string field of a table.
·         TempDb tables are a second type of temporary table, in addition to the legacy InMemory temporary table. TempDb tables can be joined to regular tables in a query.
·         Computed columns in a view.
·         Filters on queries that perform an outer join.
·         Disabled tables can be retained in the underlying database for access by external applications.
·         Best practice compiler-enforced checks are updated to reflect new features added for this release. Emphasis is on security and evaluating existing rules that generate warnings. Warnings that require action have been promoted to errors. Minor warnings that are typically ignored have been removed.
·         A form style checker tool is integrated into the Best Practice tool.
·         Enterprise Portal is now based on Microsoft SharePoint 2010. New user controls and support for Microsoft Dynamics AX 2012 features significantly enhance the usability. The developer experience has been improved.
·         New and enhanced features are available in the MorphX development environment. This topic describes:
  • Models and the model store
  • Object IDs
  • The AxUtil command line utility
  • The new development environment
  • Installation-specific IDs
·         SQL Server Reporting Services is now the primary reporting platform for Microsoft Dynamics AX 2012.
·         New features in Visual Studio Tools enable integrated development with Visual Studio.
·         New and enhanced features for Workflow include a new Workflow Editor with advanced controls, line item workflows, and automated workflows.
·         Microsoft .NET Framework is integrated with Microsoft Dynamics AX in the following ways:

  • X++ code can now be compiled into the common intermediate language (CIL) of Microsoft .NET Framework. This enables services and batch jobs to run faster.
  • .NET interop to X++ is now supported. Microsoft Visual Studio can now automatically generate C# (or Visual Basic) code for proxy classes that wrap X++ classes and tables.
  • Events are now supported in X++. The AOT provides useful nodes that make implementation easier. Events can be used to reduce the need to change custom code when you upgrade to newer versions of Microsoft Dynamics AX. Event handler methods can be written in X++ or in any Microsoft .NET Framework language.
  • Attribute classes can be used to add metadata to classes, tables, and methods.
  • The X++ language has the new keywords as and is. You can use the is keyword to test for inheritance relationships during run time. You can use the as keyword to verify the correctness of your downcast assignments during run time. 

No comments:

Post a Comment