DAX2012R3CU9 – DIXF – Automate import/export without customizations

The Microsoft Dynamics AX 2012 Data Import/Export Framework(DIXF) is an AX module import and export data in Microsoft Dynamics AX. We often use it in data migration projects to load legacy data from old systems. I was wondering if I could use DIXF as an automated integration, without any customizations. I wanted to see if I could have a folder where new customers are dropped in a folder, and then the DIXF automatically picked up the file, and imported it.

My first step is to have a small and minimalistic Excel sheet, that users can paste in the new customer records. This is how my Excel sheet looks like:

Most of these customers exists from before, but the last record is a new customer that don’t exists in my database.

The recommended process of setting up an import/export process is described here.

The first step is to create a source data format:

I then determine what entity to use, and create a target entity

When I do this, the mapping is done automatically for me, and I don’t have to understand all the database related complexity.

My next step is to create the processing group


I then click on the Entities in the processing group, and I select my created entity and that I want to use my created Excel source data format. I also select a sample file to see if the mapping is OK.

I then just check the mapping from Excel to the staging format, and make the necessary corrections.

My next step is to go back to the processing group, and to make the necessary batch job for automatic processing.

As you see here, I set the “type” to Directory, that DIXF will scan for new files. I also specify directories for processing, completed and error. I have therefore created the following directory structure for each integration:

The other important thing is the “Execute target step”. This this used for also executing the step that transfers data from the staging table to the target tables.

I then want this to be work in batch, so I enable the batch processing.

And then I need to wait for an entire minute……… I then saw that the file was moved from the 1_new folder, and ended up in the ¤_Completed folder.

I also see in the execution history, that the files was imported into the staging tables, and then imported into the target tables.

In my customer overview, I now see that I have a new customer, but is also made sure that other related data as addresses, and phone etc was created.

This concludes how you can use DIXF to automatically import data. What I can now do to import data, is just to create my Excel file, and then dump it into the right folder (.\1_New), and then the batch system take care of the test.

If you wonder all entities that are “out-of-the-box” supported from Microsoft, then take a look here. If still something is missing, you can always ask a developer to assist in creating the DIXF entities you need.

Happy DIXF’ing J


11 thoughts on “DAX2012R3CU9 – DIXF – Automate import/export without customizations

  1. Hi kurt
    I had two records one correct and the other incorrect in case the whole file went to the error folder the correct record dint get inserted ..I had like the account no blank for the error record.

    Can we have only the error records in the excel file? how can we handle this.

    Liked by 1 person

  2. I followed the process as you suggested but At the end of the process the journal is not getting posted. Does this process automatically post or should i call the class that posts the data?



  3. Pingback: AX7 - My top 12 highlights - Patrick Mouwen

  4. Pingback: AX7 – My top 12 highlights - Microsoft Dynamics AX Community

  5. The Processing Directory, Complete Directory and Error Directory boxes are not “enabled” and will not allow me to specify a directory. What am I doing wrong?


  6. Hi Kurt,

    Thanks for the article.

    During customisations / user requirement , I have come across a requirement where in i need to import data for tables that don’t have unique index. Or Tables have primary index as “Recid”.

    As we know DIXF/DMF works on “unique index” concept to insert/update the data to target table.
    I have always been in thinking whether we can use DIXF for updating the data in target table which don’t have unique index.

    Standard example would be: Importing data to table: “DimensionAttributeValueTotallingCriteria”, which does not have an unique index but the primary index is “Recid”.
    In case of “DimensionAttributeValueTotallingCriteria” i could create a DIXF template, but i would like to know if you have come across anything as such and do we have solution in standard for this to refer to.

    Do let me know your inputs.



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.