Skip to main content

Create a custom data import export framework entity[AX 2012]

Previously I had created a simple job to import Ledger alias. This post I will look at doing the same with the Data import export framework.

There is no entity in the DIEF (Data import export framework) to import ledger alias. So, we have to create a new one.

You can follow the Microsoft technet article but I will show you some screenshots here.

http://technet.microsoft.com/en-us/library/jj933277.aspx

One big thing you will realise is that it isn’t that straight forward for a non-developer. But for a developer it should be relatively easy to create a powerful import entity.

1. Click on Data import export framework > Common > Custom entity wizard

Select or enter the table name – in this case it is DimensionAlias.

DA2013-06-17_1459

2. Suggested names and options are set. Leave the default.

DA2013-06-17_1500

3. You will get a message about ForeignKey relationships. Just click yes.

DA2013-06-17_1504

This will take some time. A few minutes.

4. You will get errors.

DA2013-06-17_1512

5. A private project will be created. In my case it didn’t create all the elements it was supposed to. But that's easy enough to finish off manually (my preferred method).

DMF2013-06-21_1941

6. Field group – If you have any generate methods. Then you have to setup a Field group for them. The suffix number you see will set the sequence

DMF2013-06-21_1937

7. Title fields – make sure you set the title fields. Otherwise you will run into some errors.

DMF2013-06-21_1939

8. DMF class required – writing code for all your generate methods.

DMF2013-06-21_1940

That is it. You are ready to set it up and start using it.

You can download the full xpo project and start using it. Hopefully this blog gives you an appreciation for Data Import/Export Framework.

Download the xpo project

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