Data Migration Tool



center4500452120Data Migration Tool11540067000Data Migration Toolcenterbottom ? 1154000 ? center790007945755AX2009 – D365Bergamo, Martina1154000AX2009 – D365Bergamo, Martinaright23002311402019760098002019Contents TOC \o "1-3" \h \z \u Prerequisites PAGEREF _Toc20995310 \h 2Installation PAGEREF _Toc20995311 \h 2Install DIXF service PAGEREF _Toc20995312 \h 2Copy binaries PAGEREF _Toc20995313 \h 2Install DMT components for AX2009 PAGEREF _Toc20995314 \h 3Combined XPO file PAGEREF _Toc20995315 \h 3Application hotfix PAGEREF _Toc20995316 \h 3Register an application with the Microsoft identity platform PAGEREF _Toc20995317 \h 3Step 1 PAGEREF _Toc20995318 \h 3Step 2 PAGEREF _Toc20995319 \h 3Configuration PAGEREF _Toc20995320 \h 4Configure connection PAGEREF _Toc20995321 \h 4Configure default maps PAGEREF _Toc20995322 \h 4DefaultValue.xslx PAGEREF _Toc20995323 \h 5Financial dimension PAGEREF _Toc20995324 \h 6Create migration group PAGEREF _Toc20995325 \h 7Entities form – add entities to the group PAGEREF _Toc20995326 \h 7Export package PAGEREF _Toc20995327 \h 9Delta run PAGEREF _Toc20995328 \h 9New entities PAGEREF _Toc20995329 \h 10Appendix PAGEREF _Toc20995330 \h 11PrerequisitesMicrosoft 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 2008SQL Server 2012 and laterNo Microsoft Office on the VMAccess engine 32-bitAccess engine 64-bitMicrosoft Office 32-bitAccess engine 32-bitAccess engine 64-bitMicrosoft Office 64-bitAccess engine 32-bit and 64-bitAccess engine 64-bitMicrosoft 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 serviceGo 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.When the wizard starts, select?Next.Accept the license terms, and then select?Next.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.Select the SQL Server version, and then select?Next.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.dllInterop.Shell32.dllInstall 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 bined XPO fileExtract the combined XPO file from?DMT_V1.0\CombinedXPO.Import the combined XPO file into AX 2009.Copy the label file from?DMT_V1.0\Label file?to the?Program Files\Microsoft Dynamics AX\50\Application\Appl\<NameOfYourDeployment>?folder.Restart the Application Object Server (AOS) instance.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 hotfixGo to?DMT_V1.0\ApplicationHotfix\DynamicsAX2009-KB4010403-SP1, right click?setup.exe, and then select?Run.In AX 2009, in the Application Object Tree (AOT), notice that the?LegalEntityId?field has been added to the DMTCustomerAddressView and DMTVendorAddressViewviews.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: 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 dataConfigurationConfigure connectionIn AX2009, select Data migration > Setup > Connection details, and enter the following information:DIXF service host: the host name of the DIXF service installationService url: D365 applicationTenant url: Azure AD auth tenantService app Id: the ID of the application registered in the step 1Client secrete: the secret generated for the application in step 1Validate and close the form.Configure default mapsIn AX2009, select Data migration > Setup > Configure default maps, and enter the following information:Default configuration: the path of the DefaultValue.xlsx provided by MicrosoftExport package file path: a folder to export the packages created in AX2009Apply data conversion: apply conversions defined in the system under Data migration > Setup > Data conversionText 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 exportSQL user / SQL password: SQL authentication credentials for the AX2009 databaseSystem language: the language for the export (also to formatting dates and numbers)Chart of accounts delimiter: the delimiter for financial dimension stringIncrement: increment value for the system line numberAfter 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:SourceTable: the name of the table to migrate (AX2009)TargetEntityName: the name of the target table (D365)SourceQuery: if the entity must use a query to select a range of data, you have to specify it here. SourceField: to specify new fields (in D365) not present in AX2009SourceStrValue: 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.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.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 shotApply sequence: AX generates the sequence automatically (considering dependencies)Field mapping: shows the mapping from AX2009 and D365 tablesTarget entity attribute: for each field of the target entity, you can see field type and field sizeReset field mapping: to reset the mappingDisplay 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. Execution unit: different executions are executed in parallelLevel in execution unit: different level in the same execution are executed in parallelSequence in level: the sequence defines in which order, entities in the same level are processed1.1.1 Sales tax codes1.1.2 Sales tax code values1.1.3 Sales tax code limits1.1.4 Sales tax groups1.1.5 Sales tax group details1.1.6 Sales tax item groups2.1.1 Sales tax exempt number3.1.1 Sales tax exempt code4.1.1 Sales tax reporting codesOnce the group is complete, close this form.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.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).Appendix ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download