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.
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.
PROS:
- It is some what configurable to allow multiple sources. ODBC, CSV, Excel
- The mapping is configurable – depends on how you develop it though
- Leverage the existing framework – batchable, multi threading etc.
CONS:
- 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.