Detect code upgrade conflicts

  • Article

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

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

Code upgrade conflicts occur when your customized legacy code cannot be safely used on a new Microsoft Dynamics AX target system without review and, in many cases, modification. This task opens the Detect code upgrade conflicts form, which offers options to perform various types of code conflict analysis and resolution. Conflicts are organized into development projects that allow for easy comparison of conflicting application object versions. The form also allows you to resolve some upgrade conflicts automatically.

For developer documentation about code upgrade in Microsoft Dynamics AX 2012, see the downloadable code upgrade white papers. See also Inside Microsoft Dynamics AX 2009, Chapter 18: “Code upgrade,” pp. 623–644.

Options for detecting and resolving code conflicts

The functions available from the Detect code upgrade conflicts form are listed below. You can:

  • Scan metadata (code, properties, form structure) and search for inconsistencies between the baseline and target versions.

  • Delete customized application objects where the customizations duplicate standard Microsoft Dynamics AX code.

  • Automatically merge versions of methods contained in multiple releases and customizations of Microsoft Dynamics AX.

  • Resolve object property conflicts automatically in favor of customer changes.

  • Scan for conformity to best practices in designing table and project references (IDs).

  • Analyze custom code on the target system for rule conflicts. This analysis is based on the code conflict rules that you imported during the Configure rules for code upgrade step.

  • Auto-resolve code conflict patterns that are discovered.

Code conflict projects

Projects that may be created include the following:

Type of analysis

Project created

Layer conflict

Private project AxUpgradeLayerConflicts_<layer>

Framework (ID reference) conflict

Private project AxUpgradeRecIdConflicts_<layer>

Pattern (rule) conflict

Private project AxUpgradeRuleConflicts_<layer>

Note

Although no baseline database is required to run code pattern detection, analysis of layer conflicts requires that you configure a baseline database before you run this task. Follow these steps to configure the baseline database:

  1. Close the Microsoft Dynamics AX client.

  2. Open the Microsoft Dynamics AX 2012 Server Configuration utility (Start > Administrative Tools > Microsoft Dynamics AX 2012 Server Configuration).

  3. If there is no editable configuration, create a new one.

  4. On the Database Connection tab, set the Baseline database name value so that it is the same as the Database name value.

  5. Restart AOS.

  6. Reopen the Microsoft Dynamics AX client, and continue with the upgrade.