Skip to main content

Data Import/Export Framework for Integration

Data Import/Export Framework (DIXF) is more than just initial data load tool. We have seen in the recent R3 release that Microsoft has extended the capability to include Master Data Management (MDM).

Now I will talk about a common request.


CSV file is generated every day and saved to a directory. We need to process these files by importing them into AX. If it is successful move it to the Success folder, if it fails move it to the failed folder.

Old solution without DIXF:

Create a class that is batchable that reads from the folder and do all the coding for moving the file around etc.

New solution with DIXF:

Create a new DIXF entity to process the file. Make sure the Source and Staging fields line up.


In your staging to target – do all the work in the Generate method.


Then when you process the entity you can configure it to run on a directory.


Lastly, schedule the staging clean up job. This ensures the staging tables are cleared up and it doesn't grow too much.



  1. It is some what configurable to allow multiple sources. ODBC, CSV, Excel
  2. The mapping is configurable – depends on how you develop it though
  3. Leverage the existing framework – batchable, multi threading etc.


  1. It does a full insert/update – even if there are no changes in the records. This how ever could be done via code. No different if you where building this from scratch.


I hope this is an idea that catches on and Microsoft develops DIXF to support these types of scenarios. As I believe DIXF is really much more than just importing data before go live and forgetting about it. It is a framework that could be used for EDI solutions, it is a framework that can be used to solve our common data import issues.

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

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.