Summary

The Delivery Reminder printing process in Dynamics 365 Business Central is not aligned with the standard document output pipeline used by other sales documents (e.g., Sales Invoices). This inconsistency limits extensibility and forces partners to implement document-specific workarounds.

Detailed Description

In Business Central, most document types integrate consistently with the standard Report Selections / Document Sending Profile pipeline. This pipeline provides a rich set of Handled-pattern events, including extensibility points immediately before report execution, allowing extensions to intercept, redirect, archive, route, or replace document output without modifying base code.

However, Delivery Reminder printing currently deviates from this standard approach:

• The report is executed directly using Report.RunModal(...) after filtering Report Selections.
• While there is a high-level OnBeforePrintDeliveryReminder(..., IsHandled) event, there is no extensibility point immediately before the report execution itself.
• The process does not flow through the standard Document Sending Profile / Report Selections printing methods.

As a result, document output solutions cannot integrate with Delivery Reminder printing in the same way as other document types, leading to inconsistent behavior and increased partner effort.

Requested Improvement

Please consider aligning Delivery Reminder printing with the standard output pipeline by implementing one of the following approaches:

1. Route Delivery Reminder printing through the standard Document Sending Profile and Report Selections printing methods, consistent with other sales documents
2. or
3. Introduce an equivalent Handled-pattern event immediately before Report.RunModal(...) is called, including:

• Access to the current Report Selection
• Access to the record or Variant being printed
• An IsHandled parameter to allow full interception

Business Impact

This change would:

• Reduce partner development effort per document type
• Improve maintainability and lower upgrade costs
• Enable consistent, extension-friendly output solutions
• Strengthen Business Central’s extensibility model and developer experience