1 | P a g e

Data Migration Tool

2019

AX2009 – D365Bergamo, Martina

 

ContentsPrerequisites...............................................................................................................2Installation..................................................................................................................2

Install DIXF service..................................................................................................2Copy binaries..........................................................................................................2Install DMT components for AX2009.......................................................................3Combined XPO file...................................................................................................3Application hotfix....................................................................................................3Register an application with the Microsoft identity platform...................................3

Step 1...................................................................................................................3Step 2...................................................................................................................3

Configuration..............................................................................................................4Configure connection..............................................................................................4Configure default maps...........................................................................................4DefaultValue.xslx....................................................................................................5Financial dimension.................................................................................................6

Create migration group..............................................................................................7Entities form – add entities to the group.................................................................7

Export package..........................................................................................................9Delta run.................................................................................................................9

New entities..............................................................................................................10Appendix.................................................................................................................. 11

2 | P a g e

Prerequisites Microsoft SQL Server 2008/2012/2014/2016. The Microsoft .NET Framework version 4.5 or later. Microsoft SQL Server machine that has Microsoft SQL 2012 Native Client

installed. The Microsoft SQL Server Integration Services (SSIS) service is installed and

running on the machine where the DMT service will be installed. SQL Server authentication must support both SQL authentication and Microsoft

Windows authentication. Microsoft Access database engines that follows the version guidance in the

following table.

  SQL Server 2008 SQL Server 2012 and laterNo Microsoft Office on the VM Access engine 32-bit Access engine 64-bitMicrosoft Office 32-bit Access engine 32-bit Access engine 64-bitMicrosoft Office 64-bit Access engine 32-bit and 64-bit Access engine 64-bit

Microsoft Dynamics AX 2009 SP1 5.0.1000.52 or later. The prerequisite patch (axpatch.exe) installed. To find the patch, from the

location where you downloaded and extracted the zip file, go to<prerequisiteforpatch><application>

InstallationInstall DIXF service

1. Go to the location where you extracted the zip file, and then, in the DIXF msi folder, right-click DIXF_Service_x64.msi, and select Run.

2. When the wizard starts, select Next.3. Accept the license terms, and then select Next.4. Select an account for the service, and then select Next. The account should

have admin rights. If you select the Network Service check box, verify that the network service account has admin rights. Otherwise, clear the check box, and enter an admin account user name and password. Then select Next.

5. Select the SQL Server version, and then select Next.6. Select Install, and then, when the wizard is completed, select Finish.

Copy binariesGo to the location where you extracted the zip file, and copy the following files to the Program Files (x86)\Microsoft Dynamics AX\50\Client\Bin folder:

Microsoft.Dynamics.AX.Framework.Tools.DMT.dll Interop.Shell32.dll

3 | P a g e

Install DMT components for AX2009There are two ways to install the DMT. You can use the combined XPO file or an application hotfix. If you are using a Microsoft Dynamics Lifecycle Services (LCS) Implementation project, use the application hotfix. Installation takes approximately seven hours.

Combined XPO file1. Extract the combined XPO file from DMT_V1.0\CombinedXPO.2. Import the combined XPO file into AX 2009.3. Copy the label file from DMT_V1.0\Label file to the Program Files\

Microsoft Dynamics AX\50\Application\Appl\<NameOfYourDeployment> folder.

4. Restart the Application Object Server (AOS) instance.5. In AX 2009, select Data migration > Setup > Compile and synchronize

DMT application.Note that the combined XPO file is imported into the layer that the user is signed in to.

Application hotfix1. Go to DMT_V1.0\ApplicationHotfix\DynamicsAX2009-KB4010403-SP1,

right click setup.exe, and then select Run.2. In AX 2009, in the Application Object Tree (AOT), notice that

the LegalEntityId field has been added to the DMTCustomerAddressView and DMTVendorAddressViewviews.

3. Select Data migration > Setup > Compile and synchronize DMT application.

Register an application with the Microsoft identity platformStep 1 Register a new app in Azure ADHow to: https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-aStep 2In the D365 application, register the new app created in the step 1 in Azure Directory ApplicationsInsert the application ID from step 1, a name of the application and the user used by this application to access data

4 | P a g e

5 | P a g e

ConfigurationConfigure connection

In AX2009, select Data migration > Setup > Connection details, and enter the following information:

DIXF service host: the host name of the DIXF service installation Service url: D365 application Tenant url: Azure AD auth tenant Service app Id: the ID of the application registered in the step 1 Client secrete: the secret generated for the application in step 1

Validate and close the form.

Configure default maps

In AX2009, select Data migration > Setup > Configure default maps, and enter the following information:

6 | P a g e

Default configuration: the path of the DefaultValue.xlsx provided by Microsoft

Export package file path: a folder to export the packages created in AX2009

Apply data conversion: apply conversions defined in the system under Data migration > Setup > Data conversion

Text qualifier: Enter the delimiter used if the text values in a row contain the character that you are using as a row or column delimiter. For example, if your organization names include commas, but you are using commas as column delimiters, you should enter another delimiter to use for text values. In this example, you might want to use a double quotation mark (").

Export format: the type of the file for the export SQL user / SQL password: SQL authentication credentials for the AX2009

database System language: the language for the export (also to formatting dates and

numbers) Chart of accounts delimiter: the delimiter for financial dimension string Increment: increment value for the system line number

After the validation is completed, click generate maps.

DefaultValue.xslxThis file is used by the system in order to generate the mapping between source and target tables. The columns are:

4. SourceTable: the name of the table to migrate (AX2009)5. TargetEntityName: the name of the target table (D365)6. SourceQuery: if the entity must use a query to select a range of data, you

have to specify it here. 7. SourceField: to specify new fields (in D365) not present in AX20098. SourceStrValue: to specify the values for new fields (in D365) not present in

AX2009Here an example. The system will select from the UnitConvert table, only records where the ItemId is empty. In AX2009, this table does not contain the two fields Numerator and Denominator, used instead in D365. For that reason, in the file are specified the two default values 1 and 10.

7 | P a g e

Financial dimensionIn AX2009, select Data migration > Setup > Financial dimension.

In this form is possible to activate/deactivate financial dimension. In AX2009, the financial dimension are stored in the system in a container. For example, each customer we have a container with the financial dimension:

In D365 the financial dimensions are stored in different tables and referenced through RecIds. For this reason, we need to pass the financial dimensions values in a single formatted string. For example, the result of the export for the screenshot above is:

Department-Cost Center-Purpose 030--Site1Further information about financial dimension in the Appendix at the end of the document.

8 | P a g e

Create migration groupA migration group defines which entities should be packaged and exported together. In a migration group, you also associate legal entities.In AX2009, select Data migration > Common forms > Create migration group. Create a new group with name and description.

In the Select Company accounts, you can select one or more companies for the export.

Entities form – add entities to the groupIn the form, click Entity. Here you can select/manage the entities for the migration group.

Activate / Deactivate all: to select/deselect all entities in one shot Apply sequence: AX generates the sequence automatically (considering

dependencies) Field mapping: shows the mapping from AX2009 and D365 tables Target entity attribute: for each field of the target entity, you can see field

type and field size Reset field mapping: to reset the mapping

9 | P a g e

Display options: here you can add 3 additional fields to this form. These three fields are used in D365 to define the sorting of the entity for the import.

o Execution unit: different executions are executed in parallelo Level in execution unit: different level in the same execution are

executed in parallelo Sequence in level: the sequence defines in which order, entities in

the same level are processed

1.1.1 Sales tax codeso 1.1.2 Sales tax code values

1.1.3 Sales tax code limits 1.1.4 Sales tax groups

o 1.1.5 Sales tax group details 1.1.6 Sales tax item groups

2.1.1 Sales tax exempt number 3.1.1 Sales tax exempt code 4.1.1 Sales tax reporting codes

Once the group is complete, close this form.

10 | P a g e

Export packageIn the form Migration group, click Export now. A dialog will open.

The system sets automatically the Job ID, the text qualifier, the export format, the flag export data as package and the export file path. You can set a description for the job.

Delta runWith this option, you have to select a Previous Job ID. The system will check the delta between the current export and the previous export. He creates a package only with the differences.

11 | P a g e

New entitiesFor new entities in D365, you have to generate the mapping in AX2009.To create the entity in AX2009 you have to add the name of the source/target table in the .xlsx file located here (field Default configuration – point 1):

Add a new line and insert a name for SourceTable and TargetEntityName. If you need, you can also specify a query and default values for new fields present in D365 but not present in the SourceTable.Once you have modified the file, you have to regenerate the maps (point 2).

12 | P a g e

Appendix

13 | P a g e

14 | P a g e

15 | P a g e