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.

Scenario

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.

Options

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

image

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.

image

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).

image

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

image

Result

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

image

Download the xpo

Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...
Read more