AX 2009 to AX 2012 Upgrade

Tagged: ,

This topic contains 2 replies, has 3 voices, and was last updated by  Locus IT 6 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #20577

    Ruth Smith
    Participant

    I have an upgrade from AX 2009 to AX 2012, and a code upgrade is recommended can someone give me an overview of the steps to code upgrade.

    #20915

    Locus IT
    Participant

    Hello Ruth,

    Planning for a code upgrade. Each code upgrade is different. There are three key considerations for your code upgrade:
    1. New features that replace existing customizations. In some cases new Microsoft Dynamics AX 2012 features will replace your customizations. When planning a code upgrade, you must identify these customizations and choose not to upgrade them because they have been replaced by Microsoft Dynamics AX 2012 features.
    2. Microsoft Dynamics AX 2012 refactoring that impacts your customizations. In some cases in which Microsoft Dynamics AX 2012 features have changed, the changes will impact your customizations. You must identify which changes impact your customization. There are two categories here:
    • Required changes
    • Optional changes Further guidelines are provided below.
    3. Upgrading of standalone partner code. In some cases, partners have added code (tables, classes, reports, or forms) that do not customize Microsoft code. In this case, there are no direct dependencies on Microsoft. The work here is to ensure that the metadata/code runs and compiles on Microsoft Dynamics AX 2012. Partners can optionally uptake Microsoft Dynamics AX 2012 features in their metadata.
    When planning your code upgrade, you will need to consider which Microsoft Dynamics AX 2012 changes are required, and which are recommended.

    Setup and configuration steps
    1. Before you begin
    • You must have a valid developer license installed on the system in order to view the code upgrade checklist.
    • Before you start to upgrade your code to Microsoft Dynamics AX 2012, remember to create and keep a backup of the code you plan to upgrade (for example, your Microsoft Dynamics AX 4.0 or Microsoft Dynamics AX 2009 system).
    2. Baseline database
    3. Create baseline database during setup
    4. Choose an upgrade checklist
    5. AOD code upgrade

    AOD upgrade process
    To import AOD files to the baseline model store
    1. Create a folder named Old on the Microsoft Dynamics AX 2012 server in the following location: %ProgramFiles%\Microsoft Dynamics AX\60\Server\\bin\Application\Appl\Standard Standard is the default value. This path is the same as the Server Config value.
    2. Copy the AOD files from the source system to the folder created in Step 1. Note: You must copy all AOD files, even for the Microsoft layers.
    3. Some layers have been renamed with a new prefix in Microsoft Dynamics AX 2012. Rename any existing AOD files to the name of the new layer
    4. From the Import Microsoft AOD files into the baseline model store dialog box, select the name of the layer file to import. You must import the Microsoft layers at the bottom of the list first, and then the higher-level layers. Each layer must be imported one at a time
    5. From the Import AOD file into the baseline model store dialog box, select the lowest-level layer file that you want to upgrade.
    6. Click OK to import the AOD file.

    To import AOD files to the new model store
    1. Copy the layer file that you want to upgrade from the source system to this folder: %ProgramFiles%\Microsoft Dynamics AX\60\Server\ \bin\Application\Appl\Standard Do not copy the AOD files for the Microsoft layers into this folder.
    2. Some layers have been renamed in Microsoft Dynamics AX 2012. Rename any AOD files to the name of the new layer
    3. From the Import AOD files into the new model store dialog box, select the name of the layer file to import.
    4. Select the model to import the AOD file into.
    5. Click OK to import the AOD file.
    6. Restart the AOS.
    7. Continue to the next steps in the code upgrade checklist for the layer file that you have just imported.
    8. After you have completed the code upgrade checklist for one layer, repeat this procedure for the next layer file. Remember that lower-level layer files must be imported before higher-level layer files.

    To import label files to the new model store
    1. On the Microsoft Dynamics AX 4.0 or Microsoft Dynamics AX 2009 source system, use the Label file Wizard to create a label file for the layer that you are working with.
    2. Copy the label file to the Microsoft Dynamics AX 2012 system.
    3. From the Select file dialog box, select the name of the label file to import. You should select the label file that corresponds to the AOD file that you imported in the code upgrade checklist.
    4. Click OK to import the label file.
    5. Continue to the next step in the code upgrade checklist for the label file that you have just imported.
    6. After you have completed the code upgrade checklist for one layer, repeat this procedure for the next layer’s label file, after you have imported that layer. Remember that lower-level label files must be imported before higher-level label files.

    #20588

    John
    Participant

    Below you will find a list of tasks that you should complete when upgrading your existing Dynamics AX system. If any of the following tasks are not done correctly, the upgrade process will be a mess if not a failure.

    1. Code Upgrade: With the major changes introduced, this task will be one of the lengthiest tasks. Depending on the amount of customization required. You need AX experts to determine if the customization is needed or there is a new feature replacing it.
    Note: All existing AX reports need to be replaced with AX SSRS reports.
    2. Security Upgrade: This area has completely changed and needs to be redone.
    3. Reliable Hardware: If not planned right, it might affect the performance of the upgrade process. Remember, good hardware helps your upgrade process to run faster.
    4. Data Migration: As I mentioned above with the changes to database structure, a thorough testing is required to determine the validity of data being migrated. This requires running reports in both old and new AX systems and comparing the results. Sometimes data massaging or script fixing is required to guarantee no data is being missed.
    5. Data upgrade process (upgrade scripts): The processing time required to run upgrade scripts will impact the planning for your Go-Live date and the amount of time required to take the production system down. These scripts can be divided into 2 major categories: scripts that run in parallel to production operations and scripts run in single user mode, meaning no one is allowed to access production AX.
    6. Validating AX 2012: You will have to develop a thorough plan to help you validate the AX upgrade, make sure to involve super users in this task to get their approval. This is the most critical task in measuring upgrade success.

    Finally, whether you are considering to upgrade your existing Dynamics AX system in-house or with the help of a Microsoft Dynamics AX partner, I recommend that you thoroughly go over AX 2012 upgrade whitepapers, making sure you understand the process, lay out a clear project baseline, and finally, select a capable team to make this project a success!

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Skip to toolbar