DatA Glove

DIEF setup in AX 2012

CH.Lakshmi

10/15/2014

[Type the abstract of the document here. The abstract is typically a short summary of the contents of the document. Type the abstract of the document here. The abstract is typically a short summary of the contents of the document.]

Table of ContentsDIEF setup in AX 2012..................................................................................................................................0

DIEF: Data Import/Export Framework.........................................................................................................2

Architecture:........................................................................................................................................2

Import/Export process:........................................................................................................................2

Define the source format file:..............................................................................................................2

Processing group.................................................................................................................................3

Entity File:............................................................................................................................................4

Run the Import/Export process...........................................................................................................7

DIEF: Data Import/Export FrameworkThe data migration framework (DMF) is a tool provided by Microsoft to make data migration of complex data structures to easier and more standardized.

This tools is available from AX 2012 cu7 or later for AX 2012 R2

Other tools are available (Ex: AIF, Excel-add in...), but the DMF is definitely a big setup forward to simplify and optimize data migration.

This document will talk about basic framework and components of the data migration framework.

Architecture:

The following diagram shows the architecture of the Data Import/Export Framework.

The Data Import/Export Framework creates a staging table for each entity in the Microsoft Dynamics AX database where the target table resides. Data that is being migrated is first moved to the staging table. There, you can verify the data, and perform any cleanup or conversion that is required. You can then move the data to the target table or export it.

Import/Export process:1. Define the source format file2. Processing group3. Entity file4. Run the Import/Export process

Define the source format file:Determine the source data to export/ Import and create the source data format (width, Choose Delimited and Column Delimiter for text file, XML file and Microsoft excel file).Data Migration Framework > Setup > Source data formats

The Application tab contains application specific setup information that determines how imported data elements are processed. We can select the dimension code etc...

Processing groupIn processing group set the entities which should be Imported/Exported. Processing group set of entities that must be processed sequence. The entities in a processing group are exported together, or they are imported together from source to staging and then from staging to target.

Data Migration Framework > Common > Processing group

1. Create a new record in Processing group then click on Entities button

Entity File:Entity will determine the data mapping. We can use the existing entity or can create new Custom Entity.

1. Create a new record. In this example I created one for a Vendor import. The Sample file path field will be blank.

Note: You can use the demo file located under the installed folder. C:\Program Files\Microsoft Dynamics

AX 2012 Data Migration Framework (Beta)\Demo Files

If you use the Demo files, then skip steps 2to 4. If you want to modify the columns, then do steps 3 to 5,

as it will ask you if you want to modify the existing file format.

2. Generate a sample file by clicking on Generate source file button. Follow the wizard and select the

fields to import

3. Then click the Generate sample file button. This will open up the sample file in notepad.

Click Finish when done.

4. Now fill in your data on the txt file.

4. Back on the main form click the Generate source mapping button. This will analyze the file and do the

mapping between the file and the staging table.

5. Now you can open and view the mapping by clicking on the Modify source mapping button.

It should looks something like this. The Source is your txt file and the Staging is your staging table in AX.

If your source file is messed up, you should be able to see it here.

6. Now validate the setup by clicking the Validate button on the main form.

7. View target mapping. This is a mapping between the Stagings’s to the Target table. This should

already be predefined. You can however modify the mapping.

Notice the Function options on the left. These are predefined methods in the class to allow you to

execute business logic. The example below, when you pass in a string of dimensions A-B-C, the

GenerateDefaultDimension function splits the string up and generates a DefaultDimension RecId. A

similar thing happens with the Generate Party, which creates all the required global address book

records to return a Party RecId.

8. Back on the main form. Click the Preview source file button. This loads up the file, to give you a

preview of your file...

Run the Import/Export process

Use the processing group options to either import or export data.

For import: you first import the data to a staging table, where you can clean or transform the data as you require. You should validate that the data appears accurate, and that the reference data is mapped correctly. You then migrate the data from the staging table to the target table. You should validate that the entity appears accurate in the target table.

For export: you also move the data from the source to a staging table, where you can clean or transform the data as you require. You then export the data either to Microsoft Dynamics AX or to a file. The first option creates a .dat file and a .def file for the data, so that it can be imported into another Microsoft Dynamics AX instance. The second option creates a flat file for the data.

1. Go back to the Processing group form and click the Get staging data. This opens up a dialog with the processing group, click OK. You will then get this form.

2. System will ask for Job ID to create a Job for running Staging Data routine. Provide an appropriate ID, Description and click "OK". See screen shot below:

D

3. Click on the Run to run client side or Click on Run on AOS to run server side. Usually, the user

account doing the import won’t have access to SQL integration servers. Use the second option

and it will run under the service account. This should run and complete without errors.

4. You can now see the staging table by going to the Execution history from the Processing group form.

From there you click the View staging data button. You can modify the staging data before you process

it to the target.

5. To process to the target, click on the Copy data to target button. Follow the options to execute the

process.

You are now done. The result should be the vendor record created.

Note: The staging data might contain business information. Therefore, we strongly recommend that you delete the staging data after the migration is completed.