Search through blog..

Sunday, October 14, 2012

What's New in Microsoft Dynamics AX 2012

Analytics for Developers:

  • The Analysis Services project wizard makes it easier to create, update, configure, and deploy Analysis Services projects. The wizard performs many of the tasks that you would otherwise have to perform manually in Microsoft Business Intelligence Development Studio (BIDS).
  • You can use Microsoft Dynamics AX views to model data in perspectives.
  • You can create Gregorian calendars to use as date dimensions in your Analysis Services project.
AOS and Database for Developers:

  • The following Application Object Server (AOS) features provide functionality for advanced applications or make it easier to write applications:
1.    Valid time state tables that contain date effective data.
2.   The UnitOfWork class to simplify database transaction management.
3.   Inheritance among tables, similar to class inheritance.
4.   Full text index support to quickly query words that are embedded in the middle of a string field of a table.
5.   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.
6.   Computed columns in a view.
7.   Filters on queries that perform an outer join.
8.   Disabled tables can be retained in the underlying database for access by external applications.

Best Practices for Developers:

  • 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.

Client for Developers:

  • New forms, controls, and data source features are added to help you customize the Microsoft Dynamics AX 2012 Windows client.
Debugging in Microsoft Dynamics AX 2012:

  • In MS DAX 2012, development can be done in both X++ and .NET managed code. The development environment you use is either the MorphX Integrated Development Environment (IDE) or the Visual Studio IDE depending on the type of development you are doing.
  • Because X++ and .NET development are integrated, debugging may require that you use the Microsoft Dynamics AX debugger and the Visual Studio debugger depending on your development scenario.
  • The different debugging scenarios include the following: (Will explain in detail in my next posts)
1.   X++ Code
2.   Managed Code
3.   Services
4.   Reports
5.   Enterprise Portal
6.   Batch Jobs

Enterprise Portal for Developers:

  • 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.

Help System for Developers:

  • You can create and publish new Help documentation.
  • The new Help server simplifies how you update and customize Help documentation.
MorphX Development for Developers:

  • New and enhanced features are available in the MorphX development environment like:
1.   Models and the model store
2.   Object IDs
3.   The AxUtil command line utility
4.   The new development environment
5.   Installation-specific IDs

MorphX Tools for Developers:

  • New and enhanced development tools are available in the MorphX Integrated Development Environment (IDE).

Organization Model for Developers:

  • You can extend organization model to support ISV or partner customization or configuration scenarios.
  • You can define new custom operating unit types.
Reporting for Developers:

  • SQL Server Reporting Services is now the primary reporting platform for Microsoft Dynamics AX 2012. The reporting tools for Microsoft Dynamics AX enable you to define reports for the Reporting Services platform.
  • Reporting Services includes a complete set of tools that help you manage and define reports.
  • Reporting Services tools work in the Microsoft Visual Studio environment and are integrated with SQL Server tools and components.

Security for Developers:

  • The security keys of earlier versions are gone from Microsoft Dynamics AX 2012. The record level security (RLS) feature will be removed from a future version of the product.
  • The new role-based security system makes security design and administration easier.
  • Responsibilities are shared between the system administrator and the developer. The developer works with the new Security node in the AOT.
Services and AIF for Developers:

  • New features are available in Services and Application Integration Framework (AIF). Together, services and AIF provide the programming model, tools, and infrastructure support for message-based integration of application functionality and data with Microsoft Dynamics AX.
Visual Studio Tools for Developers:

  • New features in Visual Studio Tools enable integrated development with Visual Studio.

Workflow for Developers:

  • New and enhanced features for Workflow include a new Workflow Editor with advanced controls, line item workflows, and automated workflows.
X++ for Developers:

  • Microsoft .NET Framework is integrated with Microsoft Dynamics AX in the following ways:
1.   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.
2.   .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.
3.   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.
4.   Attribute classes can be used to add metadata to classes, tables, and methods.
5.   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.
Post a Comment