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.

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.

 2014-08-15_1608

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

2014-08-15_1609 

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

2014-08-15_1614

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

2014-08-15_1632

PROS:

  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.

CONS:

  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.in(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