New event in procedures `ReceivablePostOnly` and `ReceivablePostAndPrint` of codeunit 7000003`

[ccastro-pwd]

Why do you need this change?

Both procedures hardcode calls to: REPORT.RunModal(REPORT::"Post Bill Group", ...)
Partners need an extensibility point to redirect the report to a custom report without modifying base code.

Describe the request

Description

Add integration events to ReceivablePostOnly and ReceivablePostAndPrint in Codeunit 7000003 ("BG/PO-Post and Print") so partners can override the report execution and run a different report.

Current procedures

procedure ReceivablePostOnly(BillGr: Record "Bill Group")
begin
    if BillGr."No. Printed" = 0 then begin
        if not Confirm(Text1100000) then
            Error(Text1100001);
    end else
        if not Confirm(Text1100002, false) then
            Error(Text1100001);

    BillGr.SetRecFilter();
    REPORT.RunModal(REPORT::"Post Bill Group", BillGr."Dealing Type" = BillGr."Dealing Type"::Discount, false, BillGr);
end;

procedure ReceivablePostAndPrint(BillGr: Record "Bill Group")
var
    PostedBillGr: Record "Posted Bill Group";
begin
    BillGr.SetRecFilter();
    REPORT.RunModal(REPORT::"Post Bill Group", BillGr."Dealing Type" = BillGr."Dealing Type"::Discount, false, BillGr);

    Commit();

    if PostedBillGr.Get(BillGr."No.") then begin
        PostedBillGr.SetRecFilter();
        CarteraReportSelection.Reset();
        CarteraReportSelection.SetRange(Usage, CarteraReportSelection.Usage::"Posted Bill Group");
        CarteraReportSelection.Find('-');
        repeat
            CarteraReportSelection.TestField("Report ID");
            REPORT.Run(CarteraReportSelection."Report ID", false, false, PostedBillGr);
        until CarteraReportSelection.Next() = 0;
    end;
end;

Requested events

[IntegrationEvent(false, false)]
local procedure OnBeforeReceivablePostOnly(var BillGr: Record "Bill Group"; var IsHandled: Boolean)
begin
end;

[IntegrationEvent(false, false)]
local procedure OnBeforeReceivablePostAndPrint(var BillGr: Record "Bill Group"; var IsHandled: Boolean)
begin
end;

Proposed Code Change

procedure ReceivablePostOnly(BillGr: Record "Bill Group")
begin
   OnBeforeReceivablePostOnly(BillGr, IsHandled);
   If IsHandled then
      exit;
    if BillGr."No. Printed" = 0 then begin
        if not Confirm(Text1100000) then
            Error(Text1100001);
    end else
        if not Confirm(Text1100002, false) then
            Error(Text1100001);

    BillGr.SetRecFilter();
    REPORT.RunModal(REPORT::"Post Bill Group", BillGr."Dealing Type" = BillGr."Dealing Type"::Discount, false, BillGr);
end;

procedure ReceivablePostAndPrint(BillGr: Record "Bill Group")
var
    PostedBillGr: Record "Posted Bill Group";
begin
    OnBeforeReceivablePostAndPrint(BillGr, IsHandled);
    If IsHandled then
       exit;
    BillGr.SetRecFilter();
    REPORT.RunModal(REPORT::"Post Bill Group", BillGr."Dealing Type" = BillGr."Dealing Type"::Discount, false, BillGr);

    Commit();

    if PostedBillGr.Get(BillGr."No.") then begin
        PostedBillGr.SetRecFilter();
        CarteraReportSelection.Reset();
        CarteraReportSelection.SetRange(Usage, CarteraReportSelection.Usage::"Posted Bill Group");
        CarteraReportSelection.Find('-');
        repeat
            CarteraReportSelection.TestField("Report ID");
            REPORT.Run(CarteraReportSelection."Report ID", false, false, PostedBillGr);
        until CarteraReportSelection.Next() = 0;
    end;
end;

Expected behavior

• Partners can subscribe to these events and set IsHandled = true to skip the default report call and run an alternative report.

Reason

This provides the same extensibility pattern already available for payable procedures, without modifying base code.

[attilatoury]

Hi @ccastro-pwd,

Thanks for submitting this extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Proposed Code Change: The event declarations are provided, but please also include AL code blocks showing the surrounding context (5–10 lines) of where each event would be raised inside the ReceivablePostOnly and ReceivablePostAndPrint procedures. This helps reviewers confirm the exact insertion point.

• Alternatives Evaluated: Please describe any existing events or extensibility patterns you have already looked into and why they are insufficient for your scenario.

• Justification for IsHandled Pattern: Please explain why a standard integration event (without IsHandled) or a direct code contribution/redesign would not satisfy the requirement, and why the IsHandled guard pattern is specifically needed.

• Performance Considerations: Please provide information on the expected execution frequency of these procedures (e.g., called once per posting, per line, in a loop) and any performance impact considerations.

• Data Sensitivity Review: Please confirm whether the parameters passed to the events (e.g., BillGr: Record "Bill Group") contain or expose any sensitive or personal data.

• Multi-Extension Interaction: Please describe any risks or conflict scenarios that could arise if multiple extensions subscribe to these events simultaneously, and how those conflicts should be mitigated.

Please update the issue with the missing details. We'll automatically re-analyze once updated.