The upgrade checklist items for preparing data and preprocessing data are designed to run in the live production system, but some users will want a different option in order to prevent any additional pressure being placed on the production system. Additionally, users may want to gain extra benefit from their test runs to capture all of the data entered from forms found under the Prepare application data for preprocessing and take advantage of the test runs for the jobs under Preprocess data on the live system.
The upgrade utility ships with a set of routines that allows all of the extra data created through the preparation and preprocessing steps to be transferred back into a database that has never run these steps. Instructions for using this process are listed in great detail in the Microsoft Dynamics AX 2012 Upgrade Guide, but will not be used in the course.
In order to use the Upgrade state transfer tool, the decision to use the tool must be made BEFORE doing any of the data preparation or preprocessing steps in the live production database. If any of these steps have already been started in the live production system, the upgrade state transfer tool cannot be used.
To find out how to use the upgrade state transfer tool, see Using the preprocessing upgrade state transfer tool or obtain the Microsoft Dynamics AX 2012 Upgrade Guide (http://www.microsoft.com/download/en/details.aspx?id=14599) from the Microsoft Download Center and search in the file for the section titled "Using the pre processing upgrade state transfer tool." Read through the entire section carefully for detailed information on how to setup the live production system and the test system to support running this process.
We currently are missing an two important steps from our documentation about using the State Transfer tool. First we did not give much explanation for a step to run on the live production system while preparing the database - listed as "Enable triggers necessary to track data". Second, the steps for Performing Post-processing tasks is missing an item describing how to move/synchronize two Number Sequences created/modified by the pre-processing and delta scripts which must be manually moved to the production database copy. This will be addressed in a future version of the utility, but not released as a hotfix. The proper steps for setting up the live production system and to oerform post-transfer tasks should be the following:
Prepare the production system - (taken from the upgrade guide linked above)
1. On the production system, import the preprocessing XPO that is appropriate for the Microsoft Dynamics AX version that you are upgrading. For more information, see Install upgrade framework files.
2. On the production system, install the upgrade-related label file (.ald) files. Also install the upgrade-related Help files (.chm) files. For more information, see Install upgrade framework files.
3. On the Preprocessing upgrade checklist, complete the Check upgrade readiness task and resolve any validation errors. Enable triggers to track necessary data, based on prompts from the upgrade readiness checks.
CRITICAL NOTE - if you are upgrading from Microsoft Dynamics AX 4.0, at this point you need to go to the AOT, navigate to Jobs, and find the Job EnableDatabaseTriggers. Either choose to Edit the job and run it from the editor or just choose to Open the job to allow it to run. This will create database triggers within your SQL database that are used to track activity related to Inventory Dimensions which is required for the delta processing to properly make sure that all inventory data can be upgraded to use Multi-site correctly once it is migrated to Microsoft Dynamics AX 2012. Customers upgrading from Microsoft Dynamics AX 2009 do not need to run this process (and the job does not exist in the UpgradeAX5.xpo file).
Perform post-transfer tasks
After the state transfer is complete, perform the following tasks.
In addition to the steps listed in the Upgrade Guide, there are steps that will allow for multiple iterations of this process to be run between two test environments before a final transfer back to the live production environment. This scenario can be used if the user has very long cycles of time between testing their delta processing and new data is frequently added to the live production system. The steps listed here describe the process and should be used along with the more expanded directions in the upgrade guide:
This is where the cycling begins:
4. In the first test environment, run through the prepare data for preprocessing forms and proceed through running the Live Preprocessing tasks.
This approach minimizes the churn on the live system by only transferring data back to the production database once, after delta preprocessing has reached an acceptable run time.
The following illustration shows the workflow for using the state transfer tool in this iterative cycle.
Thanks for this detailled article!
I have 2 concerns though:
1. Using the state transfer tool, you said some number sequences (CRM_1 é CRM_2 have to be migrated manually. Do we have to do the same for the number sequences created during the prepare data for preprocessing forms? There is a form in the checklist where we must enter a valid number sequence code for the new <GeneralJournalEntryJournalNumber> reference. I have created a new one during the setup and applied the setup for all the other companies in the system.
2. Once pasted the upgrade readiness issues, is it possible to re-run these scripts during the time of the migration (i.e between 2 deltas) to ensure the next deltas and the single-user scripts will be ok?
Hi Nicolas - the answer to your first question I am not 100% sure about, but I am almost certain that you don't have to worry about the GeneralJournal number sequence. In the upgrade tables we maintain a copy of what we think the number sequence table record should be in a separate table, and if you run a delta script we always pull the number sequence for General Journals Journal Numbers from that copy and then update the real table from there. I know there haven't been any concerns raised about it from previous cases that I am aware of.
For your second question, if you are asking if you can re-run the readiness scripts, the answer is yes you can run them as many times as you would like so you could watch for potential delta script issues - there may be times if you have opened the delta cockpit where the list of scripts got created, then you cannot go back into the readiness window because we think there is processing going on.