Skip to main content

KB2996035 - Performance issues when printing 1000s of customer account statements

A bit of a spotlight on this KB. This is not in AX2012R3CU9 but available on LCS for download.

When you are printing a large number of customer statements it can take hours to print. This can be cut down dramatically.

I don’t have perfect stats but with our testing on a TEST box. It ran 2.5 times faster. Producing over over 3000 statements in 30minutes. I think with better infrastructure we can get much better results. (12GB x 4 Cores test box – was a shared box for other services) The more cores the faster it is. clip_image002

The installer contains 2 KBs in one.

clip_image004

clip_image006

The code is generic in nature but requires that you still make a small change to the code. Not sure if this was forgotten. Add this method to the controller class of the report.

image

Final result should show you a new check box “Use parallel processing”. If this is ticked then it will multi thread and the prints will be out of sequence.

If you don’t tick or see this flag, you are not multi-threading.

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.

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

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