Skip to main content

Tips to improve Ledger journal import performance [AX 2012]

There are a number of ways of importing ledger journals but with most you will realise it is quite slow with a lot of lines (100 plus lines).

I have put a couple of tips to boost the performance. Remember these are bulk creation of journals and not posting issues. That is a whole other topic.

Tip 1.

Obvious but often forgotten. Remember that journal name setup – you have a number of options to generate the voucher number.

If you leave it to generate when it balances – then this will kill your performance.


Tip 2.

On the insert method you will there is tax calculations which are deleted and recalculated every time you insert. If you can avoid calling this method and call it only for the last line per unique journal number, voucher number, and invoice.


I won’t go into detail on how to code it.

option 1: You can add a parameter and check that.

option 2: Or you can write your code so the tax is not set – do your insert. Then set the tax groups after. But remember you will have to recalculate it for the unique journal,voucher,invoice.


ledgerJournalTrans.TaxCode            = _ledgerJournalTrans.TaxCode;
ledgerJournalTrans.TaxGroup           = _ledgerJournalTrans.TaxGroup;
ledgerJournalTrans.TaxItemGroup       = _ledgerJournalTrans.TaxItemGroup;
// need to set the tax codes after the insert because the taxes are calculated during the insert if the tax codes are set.


These are a couple of simple tips that will have an impact on the performance of your imports.

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