Data import/export framework user guide ( (DIXF, DMF) [AX 2012]
Updated: October 28, 2013
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
This topic has been updated to include information about features that were added or changed for cumulative update 7 or later for Microsoft Dynamics AX 2012 R2.
Don’t know what version you’re using? See Product versions and build numbers in Microsoft Dynamics AX.
The Microsoft Dynamics AX 2012 Data Import/Export Framework is an extension that helps you export data and import it into Microsoft Dynamics AX. Examples of the data that you can import include master data, open stock, and balances.
Different versions of Data Import/Export Framework are available. Choose the correct version for your environment based on the version of Microsoft Dynamics AX that you are running,
For AX 2012 R2, use the version of Data Import/Export Framework that is available in cumulative update 7 for Microsoft Dynamics AX 2012 R2.
For AX 2012 or Microsoft Dynamics AX 2012 Feature Pack, use the version of Data Import/Export Framework that is available from the InformationSource services download page.
Some functionality that has been added to Data Import/Export Framework in cumulative update 7 for Microsoft Dynamics AX 2012 R2 is not available in the version of the tool that is available for download on InformationSource. For more information, see What's new: Data Import/Export Framework for Microsoft Dynamics AX 2012.
The following diagram shows the configuration steps that are required before you can import entities into Microsoft Dynamics AX.
Determine whether you are importing one or more Microsoft Dynamics AX entities, whether you are importing a composite entity, or a Microsoft Dynamics AX table. The topic Migrating data using the Data import/export framework (DIXF, DMF) contains a list of entities.
A composite entity groups multiple related entities together. An example of a composite entity is a sales order and sales line entities combined together.
Composite entities support only file data sources.
A table entity enables you to migrate data from a source to a target Microsoft Dynamics AX table directly, without going through a staging table or applying any business logic.
Unlike other entities, data cannot be pushed from one source table to multiple target tables. The direct table entity must be a one-to-one mapping from source to target.
Define the data format for each entity in the source environment. The data format can be a file that is delimited or fixed width, an ODBC data source, or a Microsoft Dynamics AX table.
Determine which entities should be migrated together in a processing group.
A processing group is a set of entities that must be processed in a sequence, or that can logically be grouped together. The entities in a processing group are migrated together from source to staging, and then from staging to target.
Define the processing group.
When you define a processing group, you must identify sample data for each entity. The sample data is used to validate the source to staging mapping.
If you do not have sample data, you can use the Data Import/Export Framework to help define a template for the data, and then enter sample data in the template.
Optional: If you find data in source that is not in staging, and you want to bring the data into Microsoft Dynamics AX, you may have to modify the staging schema.
Optional: You may have to modify the staging to target mapping to align the mapping with customizations in Microsoft Dynamics AX. This step is required if, for example, you have an additional field for the customer entity.
This action can be performed at any time during configuration.
The following diagram shows the processes that run when data is copied from source to staging, and from staging to target.
Source to staging processing
When an entity is copied from source to staging, a processing group that is associated with one or more entities runs as a job.
After processing has been completed, you should validate that the entity appears accurate in the staging table, and that the reference data is mapped correctly.
Staging to target processing
When data is copied from staging to target, a job that is already defined, and that is associated with a processing group, runs.
After processing has been completed, you should validate that the entity appears accurate in the target table.
After the migration has been completed successfully, we recommend that you delete the staging data.
We strongly recommend that you delete the staging data after migration is complete. It may contain business information.