Some print management report destinations are not valid for batch processing

Some print management report destinations are not valid for batch processing warning occurs when posting and printing sales invoices in batch.

In this article we will investigate this warning but let’s first examine how posting and printing an invoice in batch differs when Print Management setup for Customer invoice is, or is not used.

Post and print invoice in batch without using print management setup

Let’s say that we select Print Archive for Invoice, Invoice (copy) and Entry certificate:

When we click the OK button, we will get the message:

If we change only one selected print destination of these three options (Invoice, Invoice (copy) and Entry certificate) to Screen, or if we actually never changed the initial value of it, which is Screen by default:

In this case we might be prompted with the following message:

However, if we reopen this form (close and open again), and we have at least one of these three options already set to Screen (e.g. Invoice (copy)), we will get this message.

You can debug this case by putting the breakpoint at the first line of code of the checkPrinterSettingsMultiThread() method of the FormletterServiceController class (the same method which causes problems when we print report in batch using the Print Management setup). You will notice that this.checkClientOutput() method causes validation of the selected print destinations for all of these three options (Invoice, Invoice (copy) and Entry certificate).

Post and print invoice in batch using print management setup

Let’s select Archive (SSRS) as a target print destination for Customer invoice.

(Note that Destination is wrongly written for the SSRS Archive print destination)

If we print the report in batch using the Print Management setup for Customer invoice (in our case the target print destination is set to standard SSRS print destination Archive):

We will get the following message:

If we change the target print destination in the Print Management setup to Screen, we would get this message:

This is because of the following code (FormletterServiceController) that is executed during the validation process:

You can see that here, when report is printed and executed in batch, we will get one of the above messages in any case. This is the standard behavior of SSRS framework and it is not related to Docentric AX.

Suggested solution

The marked lines of the above code should be replaced with the following code block:

Leave a Reply

Your email address will not be published. Required fields are marked *