1. To-Increase Dynamics 365 for Finance & Operations
  2. Connectivity studio
  3. Activities

Review and complete data migration setup
Application task

As a result of the message generation, this is generated:
  • An ODBC document based on the source table in AX2012.
  • A D365FO document based on the target table in D365 FO.
  • A message with the:
    • Default Database connector of the data migration project as source connector.
    • Default D365FO connector of the data migration project as target connector.
    • Generated ODBC document as source document.
    • Generated D365FO document as target document.
    • Mapping of the document record and record fields that exist in both the source document and the target document.
  • The message is added to the data migration setup record.
For each data migration setup record, review and complete the generated documents and message.


Standard procedure

1. Click Connectivity studio Integration Design.
2. Click Projects.
 

Note: Your currently active project is opened. This is the project as shown in the Project field on the Integration design workspace. Make sure your data migration project is selected.
3. On the Action Pane, click Design.
4. Click Migrate.
5. In the list, find and select the desired data migration record.
6. Click to follow the link in the Message field.
7. Sub-task: Review and complete source document.
  7.1 On the Action Pane, click Design.
  7.2 In the Source group, click Document.
  7.3 Review and complete the ODBC source document.
For more information, refer to See also.
  Close the page.
8. Sub-task: Review and complete target document.
  8.1 On the Action Pane, click Design.
  8.2 In the Target group, click Document.
  8.3 Review and complete the D365FO target document.
For more information, refer to See also.
  Close the page.
9. Sub-task: Review and complete message.
  9.1 In the list, click the link in the selected row.
  9.2 Review and complete the message.
For more information, refer to See also.
  Close the page.
  9.3 Close the page.
10. Sub-task: Complete data migration setup record.
  10.1 On the ODBC mapping generator page, click Edit.
  10.2 In the list, find and select the desired data migration setup record.
  10.3 Assign the applicable status to the data migration setup record.
You can only assign a status as set up for the data migration project.
  In the Status field, enter or select a value.
  10.4 If a data migration setup record and the related message and documents are reviewed and completed, you can make the record active.
On task generation, when a message is added to a task, and the related data migration setup record is:
- Active, the related message action is set to 'Run'. So, if the task is run, the message is run.
- Not active, the related message action is set to 'Skip'. So, if the task is run, the message is not run.
  Select the Active check box.
11. Close the page.
12. Close the page.

Notes

RecId

On data migration, in D365 FO, new RecIds are created for records, which do not match with the AX2012 RecIds. On migration message generation, if an AX2012 field refers to a RecId, it is assumed that the related record is already migrated. Therefore, on the migration message, the field mapping is marked as 'External reference'. Applying external references, makes it possible to link an AX2012 RecId to the related D365 FO RecId.
You are advised to check the fields that are marked as external reference. Is the related table migrated before the current table is migrated? If not, you can solve it in one of these ways:
  • Add the data migration of the applicable table to the data migration setup. Add it before the table migration setup for the current table. In this case, on the migration message, for the applicable field mapping, you can keep the 'External reference' check box selected.
  • Add the applicable table to the generated source document and target document of the migration message for the current table. Also add the related record and field mapping to the generated migration message for the current table. In this case, on the migration message, for the applicable field mapping, clear the 'External reference' check box.
For more information, refer to: Apply external reference.

Financial dimensions

Financial dimensions are also handled as RecIds. This is fine if the applicable financial dimensions are migrated before the current table is migrated.
You are advised to check the financial dimension fields. Is the related financial dimension migrated before the current table is migrated? If not, you can solve it in one of these ways:
  • Add the data migration of the applicable financial dimension tables to the data migration setup. Add these before the table migration setup for the current table. In this case, on the migration message, for the applicable financial dimension field mapping, you can keep the 'External reference' check box selected.
  • For each applicable financial dimension, add a separate field to the source document and target document. Also add the related field mapping to the generated migration message for the current table. For each financial dimension field mapping, select the Dimension set or the Ledger field option and fill in the related fields. Also, remove the remove the original financial dimension field mapping from the message.
For more information, refer to:

Related to Notes

Design data migration

 		 

See also

Provide feedback