When your printed reports yield unexpected results, one of the most common reasons are print management overrides. These overrides can be configured at the document, module, or customer/vendor level, making them challenging to identify.
In this forum post, I’ll first share a tip on quickly detecting print management overrides in your environment and later on how to pinpoint exactly where the override is using the Docentric’s tracing mechanism.
To gain insights into how Docentric Print Management tracing can help you navigate your Print Management setup using a real-life example, I invite you to read a blog post authored by one of my knowledgeable colleagues titled Figure out your D365FO Print Management setup.
Determining the presence of Print Management Overrides in your environment
Open the Docentric AX workspace and check the number of print management configurations by examining the blue tiles. The text under the blue tiles should display Count: Print management settings, indicating the total number of print management configurations in your environment, excluding overrides.
Next, click on Next count until the text changes to Count: Settings including overrides. This text indicates that the numbers on the tiles represent print management configurations including overrides.
Comparing the two screenshots, you’ll notice that the numbers differ in the Accounts Payable and Accounts Receivable modules. The second screenshot reveals one print management override in the Accounts Payable module and three overrides in the Accounts Receivable module.
While this method allows you to check the number of print management overrides in your environment, it can’t specify on which level (customer/vendor, module, or document). This is where Docentric Tracing comes into play.
Identifying overrides with Docentric Tracing
Docentric Tracing offers an exceptional solution for identifying overrides, conditional settings, copy settings, and more within your Print management setup. For a detailed understanding of its capabilities, I highly recommend consulting our comprehensive how-to manual on Docentric Tracing.
To use the Docentric Print Management Tracing, you will first need to enable to respective tracing parameters in the DocTraceParam table, which are listed below.
The DocTraceParam table can be edited in non-development environments via the link
https://usnconeboxax1aos.cloud.onebox.dynamics.com/**?mi=DocTraceParam(NOTE: the first part of the address is environment-specific).
-
PRINTMGMT: Enables identification of the print management setting used during report execution.
-
TraceToDatabase: Logs the traces in the trace log DocTraceTable table. For a detailed review or complex troubleshooting, you can export the log using the standard Export to Excel feature.
You can access the DocTraceTable via the link https://usnconeboxax1aos.cloud.onebox.dynamics.com/?mi=SysTableBrowser&tableName=DocTraceTable&cmp.
(NOTE: the first part of the address is environment-specific).
- TraceToInfolog: Displays the tracing information in the Infolog (Message bar or Action center ).
When configuring the parameters, ensure the User ID column is left empty. If the User ID is specified for a particular parameter and another user executes the report, whether synchronously or in a batch, the tracing won’t be triggered.
Once the parameters are set, you’re ready to go forward with troubleshooting. Execute the report that is yielding unexpected results and follow the guidelines below to interpret the results from the trace log.
Interpreting the Trace Log Results
As a general guideline for identifying the presence of overrides, look for the keyword override in the logs.
Upon reviewing the screenshot below, you’ll notice a clear message indicating a print management override for the PurchPurchaseOrder.Report with the on the Original Setting on the vendor CN-001.
(7/14/2023 02:11:58 pm) PRINTMGMT ON_PRINTMGMT_LOAD *** PurchPurchaseOrder.Report | Copy (Copy) | Module (Accounts payable) | Default *** PurchPurchaseOrder.Report | Original | Account override (Vendors: CN-001) | Conditional (Setting 1).
With this information, you can now review and adjust the override according to your specific business requirements, ensuring your reports produce the expected results.