[Event Request] codeunit 443 "Sales-Post Prepayment (Yes/No)" OnPostCrMemoYNBeforeConfirm

[iti-anna-malek]

Why do you need this change?

Hi,

I need a similar event for procedure PostPrepmtCrMemoYN like is in the PostPrepmtInvoiceYN to use our own confirm.

Describe the request

I need the similar event as in the previous function for posting prepayment invoices.

   procedure PostPrepmtCrMemoYN(var SalesHeader2: Record "Sales Header"; Print: Boolean)
    var
        SalesHeader: Record "Sales Header";
//Change begins
IsHandled: Boolean;
//Change ends
    begin
        SalesHeader.Copy(SalesHeader2);
//Change begins
 IsHandled := false;
OnPostPrepmtCrMemoYNOnBeforeConfirm(SalesHeader, IsHandled);
if not IsHandled then
//Change ends 
        if not ConfirmForDocument(SalesHeader, Text001) then
            exit;

        PostPrepmtDocument(SalesHeader, SalesHeader."Document Type"::"Credit Memo");

        if Print then
            GetReport(SalesHeader, 1);

        Commit();
        OnAfterPostPrepmtCrMemoYN(SalesHeader);

        SalesHeader2 := SalesHeader;
    end;

    [IntegrationEvent(false, false)]
    local procedure OnPostPrepmtCrMemoYNOnBeforeConfirm(var SalesHeader: Record "Sales Header"; var IsHandled: Boolean);
    begin
    end;

[github-actions]

Hi @iti-anna-malek,

Thank you for your extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Alternatives evaluation: Explain what existing extensibility options were considered for PostPrepmtCrMemoYN and why they are insufficient beyond referencing a similar pattern in PostPrepmtInvoiceYN.
• IsHandled justification: Describe the exact custom confirmation scenario, why bypass behavior is necessary, and why a regular event would not work.
• Performance/execution impact: Add a brief statement about expected runtime or execution impact.
• Data sensitivity/security: Add a brief statement covering any security or sensitive data considerations.
• Multi-extension interaction/conflict risk: Add a brief note on how this should behave if multiple extensions subscribe or try to control the same flow.

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

Note

Automatically generated by the Triage Agent — advisory only. An engineer will review before any action is taken.

Tip

Not accurate? Reply with /not-accurate (optional: add a short explanation). Your feedback improves future responses.

[iti-anna-malek]

There is no alternative - we can use this handler for invoices and cannot for credit memos.
We want to use our own confirm with additional options, so having two similar confirms is not a user-friendly.

[github-actions]

Hi @iti-anna-malek,

Thank you for your extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Performance/execution impact: Add a brief statement about expected execution frequency and runtime impact.
• Data sensitivity/security: Add a brief statement covering whether any sensitive data is involved or exposed.
• Multi-extension interaction/conflict risk: Add a brief note on how this should behave if multiple extensions subscribe or try to control the same confirmation flow.

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

Note

Automatically generated by the Triage Agent — advisory only. An engineer will review before any action is taken.

Tip

Not accurate? Reply with /not-accurate (optional: add a short explanation). Your feedback improves future responses.

[iti-anna-malek]

/not-accurate

[github-actions]

✅ Feedback recorded
Thanks — your /not-accurate feedback has been logged and will be reviewed.