Skip to main content

Complex grouping of records for processing [AX 2012]

In this post I will discuss complex grouping of records for processing in a batch.There are many ways to achieve this but most of the time I see developers using temp tables. I feel that is not necessarily the most best way. So, in this post I will show how you can do the same using a map and a RecordSortedList. Avoiding multiple loops through records and also avoiding temp tables.


Assume a scenario where you have to loop through unsorted records. Group them by the multiple fields including things like financial dimension value and balance. Then create a journal for each group.


This could be achieved in a number of ways. But we want the best performing and extendable solution.

  1. You could do a group by selection query but that won’t work as you have to get the balance and dimensions (which are calculations).
  2. You could use a temp table to insert all the transaction. What if the key changes a few months later. Could be costly to develop the changes.
  3. You could use a map to store the RecIds and fetch the records as you loop through the map. Now you are querying the database for each fetch. You maybe also calculating the dimensions and balances during grouping and processing.
  4. You could use a RecordSortedList to store them. In my opinion is the cleanest and best way of doing it.

I will show how to do it with option 4 – using a RecordSortedList. Below in the screenshot you have 3 classes.

  • NAVAX_Process – Main batch class that is executed.
  • NAVAX_ProcessHandler – Does the grouping of the records and storing them in their respective class instance which is group in a map.
  • NAVAX_ProcessTask – The processing task class. Has an execute method which you would put


The handler class creates a map to store a container as the key and the class instance as the value. The key is a container because we are going to group my multiple values. At the end we will loop through the map to call the execute method for each class instance that is stored.


The handler class has an addRecord method. This will do the grouping by storing the values in a key. This is where you would store the calculated values to group by (I am not doing it here but using the customer group and the delivery mode instead).


The execute method in the handler class loops through the map and calls the execute method of the class instance that was stored.



In this example I am going to show the result in an infolog.


Download the xpo

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