Skip to main content

Data Import/Export Framework–Move data from AX to another AX environment

This below is a step by step to export data from an AX environment to another environment using the Data Import/Export Framework.

Export from Source AX environment

1. Open the Source data formats form.

Create a record and select AX type.


2. Open the Processing group form and create a new record.


3. Click on Entities button.

Select your entities you want to export (Example below has Customers).


4. (Optional) You can click on the Select button to put a filter.


5. Go back the Processing group form and click the Get staging data button. This will bring up the following execution form. Click the Run. This will then pull data and place it in staging table. It will enable the buttons on the Processing group form.


6. On the Processing group form, click the Export to AX button. This will bring up a dialog, enter the file name and type.


This will generate a dat and def file.

Import into Destination AX environment (Option 1)

We will import the file using dat/def. Other options to use files.

1. Click on System administration > Common > Data export/import > import

Select your file.


There is an option on the Advanced tab. Tick the Update existing record flag if you dont want to replace some important data in your Data Import/Export Framework tables.


Click OK.

2. This will import data into the staging table and the processing group table. Ready to be executed.

3. Go the Processing group form and you should find the data already in the staging table too.

4. Click on the Copy data to target button. Follow the prompts and run it. This step will move the data from the staging table to the target destination.

Import into Destination AX environment (Option 2)

After we have our data in the staging tables. Instead of exporting to dat/def files. We will instead export to a flat file (csv).

1. In the Execution history. Click on the view staging data. This will bring up a dynamic grid showing your data.


2. Click on the Export to file button. This will allow you to select a processing group (a file format setup).

Enter your file name and click OK.


This has generated a file now that you can use for importing into your other environment.

Follow these step by step that I wrote last year to import using a file (csv).

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi