Export (0) Print
Expand All
Expand Minimize

What's new: Upgrade features [AX 2012]

Updated: April 18, 2014

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic has been updated to address upgrade to Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012 R2, and Microsoft Dynamics AX 2012 R3.

The Microsoft Dynamics AX 2012 upgrade process is designed to keep downtime to a minimum. Shorter downtime means less impact on operations and lower total cost of upgrade.

Upgrades from Microsoft Dynamics AX 4.0 or Microsoft Dynamics AX 2009 to Microsoft Dynamics AX 2012 require two computer systems that operate in parallel:

  • The source system, which remains in production for most of the upgrade process

  • The target system with the latest Microsoft Dynamics AX version

In previous versions of Microsoft Dynamics AX, all upgrade tasks were performed on a single production system, requiring the system to be offline through the entire process. Difficulties that arose had to be resolved under time pressure before business operations could resume. Now, under the source-to-target model, issues involving the upgrade of business data are mostly resolved on the source system with no interruption of operations. Similarly, procedures for upgrading customized application code are carried out on the offline target system.

When data preprocessing on the source system is complete, and the target system is ready, the source system is taken offline, the prepared business data is copied to the target system, and upgrade scripts are run. After testing, the target system can go live.

ImportantImportant

Source-to-target upgrade requires that the source system and target system be installed on separate server computers. Although side-by-side installation on a single computer is possible, we recommend that you use this approach only for testing purposes. For more information, see Hardware and software requirements.

The following diagram shows the phases of an upgrade that follows the source-to-target model.

Source-to-target upgrade model

The upgrade framework for Microsoft Dynamics AX 2012 also provides a procedure for upgrading between versions within a major release. In-place upgrades do not follow the source-to-target model. Instead, all of the upgrade tasks are performed on the production system while it is offline.

The following diagram shows the phases of an in-place upgrade.

In-place upgrade
TipTip

For information about in-place upgrades between Microsoft Dynamics AX 2012, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012 R2, and Microsoft Dynamics AX 2012 R3, see Scenario: Perform in-place upgrade to AX 2012 R2 or AX 2012 R3 and Scenario: Perform in-place upgrade to AX 2012 Feature Pack.

Previous releases of Microsoft Dynamics AX implemented upgrades on a single computer system, and a single upgrade checklist contained all the core upgrade tasks. Under the source-to-target upgrade model, there are now several checklists and related forms to help you organize upgrade tasks on the source and target systems. Additional checklists have been added for in-place upgrades that are performed between versions within a major releases.

Checklist

Description

Preprocessing upgrade checklist

Tasks that prepare data on the source system for export into the database schema of a Microsoft Dynamics AX 2012 or later system

AOD code upgrade checklist

Tasks that are involved in migrating any customized code in legacy AOD files to the model architecture of a Microsoft Dynamics AX 2012 or later system

Model code upgrade checklist

Tasks that are involved in migrating any customized code in legacy models to the most recent Microsoft Dynamics AX release

Data upgrade checklist

Tasks that are involved in upgrading imported data on a Microsoft Dynamics AX 2012 or later target system

Software update checklist

Used for in-place upgrade from Microsoft Dynamics AX 2012 to Microsoft Dynamics AX 2012 Feature Pack. In Microsoft Dynamics AX 2012 R2 and Microsoft Dynamics AX 2012 R3, the upgrade framework replaces this checklist with the Code upgrade checklist for in-place upgrade and the Data upgrade checklist for in-place upgrade.

NoteNote

The Software update checklist is still used for hotfixes and updates.

Retail POS redeployment checklist

Tasks that are involved in redeploying point-of-sale (POS) terminals after the head-office system has been upgraded to Microsoft Dynamics AX 2012 R2 and up-to-date POS software has been installed in the stores

Caution noteCaution

This checklist is removed in Microsoft Dynamics AX 2012 R3.

Code upgrade checklist for in-place upgrade

Code upgrade tasks for in-place upgrades to Microsoft Dynamics AX 2012 R2 from Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 Feature Pack

Data upgrade checklist for in-place upgrade

Data upgrade tasks for in-place upgrades to Microsoft Dynamics AX 2012 R3 or Microsoft Dynamics AX 2012 R2 from earlier versions of Microsoft Dynamics AX 2012

In a source-to-target upgrade, the most labor-intensive phase is data preprocessing. If you follow best practices, you will perform your upgrade first on a non-production system. Therefore, you will spend considerable time completing data preprocessing on a test source system. The upgrade state transfer tool lets you take full advantage of the results of that effort by transferring the preprocessed data from the test system to your production system. For more information, see Using the preprocessing upgrade state transfer tool.

The Compare data upgrade row counts task in the Data upgrade checklist checks the data integrity on the Microsoft Dynamics AX 2012 target system after an upgrade. Row counts that are correctly correlated among the source, shadow, and target tables suggest, but do not confirm, that the bulk copying and data upgrade were completed successfully. For more information, see Compare data upgrade row counts.

This feature is provided by Microsoft Dynamics AX 2012 R3 and Microsoft Dynamics AX 2012 R2 only.

The code upgrade toolset for detecting and resolving conflicts between standard and customized code now provides code analysis based on code conflict rules. The rules describe code conflicts involving changes in X++ classes and methods, and provide suggested resolutions. You can add your own rules to the ones provided by Microsoft. You have the option of allowing rule violations to be resolved automatically, or you can open a development project that is created and resolve the conflicts manually. For more information, see Using the preprocessing upgrade state transfer tool.

Microsoft Dynamics AX 2012 R3 introduces two additional enhancements related to code upgrade.

  • In the code upgrade tool, you can now elect to allow multiple versions of some methods to be merged automatically during upgrade. For information, see Detect code upgrade conflicts (form).

  • The command-line tool AxBuild provides speedier code compilation than the standard AOT compilation utility. For information, see Compile application.

This feature is provided by Microsoft Dynamics AX 2012 R3 and Microsoft Dynamics AX 2012 R2 only.

As of Microsoft Dynamics AX 2012 R2, data isolation or tenancy is enabled by means of data partitions. For example, an organization that is a holding company has several subsidiaries. If the management of the organization does not want employees of one subsidiary to have access to the data for other subsidiaries, data partitions can provide the boundaries that are required for data isolation but enable the metadata that supports business processes to be shared.

When upgrading from Microsoft Dynamics AX 4.0 or Microsoft Dynamics AX 2009, it is important that you first evaluate whether you require data isolation between companies. For example, the source system may have used companies as a means of data isolation. However, there is much data that is shared between companies in Microsoft Dynamics AX 2012 R3 and Microsoft Dynamics AX 2012 R2. For example, products and parties are global for all companies in a partition. If you do not want such data to be shared, you must create additional partitions. In any case, metadata such as role definitions will be shared across all partitions.

During the upgrade process, you will be given the option to create new partitions. If you choose to create new partitions, you will then map companies from the source environment to partitions in the target environment. If you do not have to isolate data between companies, you do not have to create additional partitions. The default partition that is created during installation is sufficient for your requirements.

For more information, see the product documentation.

This feature is provided by Microsoft Dynamics AX 2012 R3 and Microsoft Dynamics AX 2012 R2 only.

During minor-version upgrade to Microsoft Dynamics AX 2012 R3 or Microsoft Dynamics AX 2012 R2 from AX 2012 or AX 2012 Feature Pack, the single Microsoft Dynamics AX database will be split into two databases, one for business data and one for application metadata. This change enables easier maintenance and backup of the databases.

This feature is provided by Microsoft Dynamics AX 2012 R3 and Microsoft Dynamics AX 2012 R2 only.

Upgrade is supported for internationalized versions of Microsoft Dynamics AX including versions for the following countries or regions:

  • Brazil

  • China

  • Eastern Europe/Russia

  • India

  • Japan

This feature is provided by Microsoft Dynamics AX 2012 and Microsoft Dynamics AX 2012 R2 only.

Upgrade of retail functionality requires redeployment (replacement and reconfiguration) of the legacy POS software on each terminal in each store. You must perform this redeployment during a tightly constrained time window to avoid disrupting retail activities. Although previous releases required that all stores be upgraded at the same time, Microsoft Dynamics AX 2012 and Microsoft Dynamics AX 2012 R2 support operations using two versions of Microsoft Dynamics AX POS register software at the same time. Multi-version support lets upgrade administrators upgrade one store at a time while maintaining normal operations in stores that are still awaiting upgrade.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft