[Event Request] Codeunit 1402

[krasivarna]

Why do you need this change?

Hello This event publisher will use to set in record Purchase Credit Memo Header some fields. I review another codeunit for cancel posted sales credit memo. In this codeunit is exist such publisher

Describe the request

I paste the procedure of codeunit 1402 "Cancel Posted Purch. Cr. Memo". Between code I shall add the new lines which marked with comment "new line". In the end of codeunit must add new publisher OnBeforeTestCorrectCrMemoIsAllowed

procedure TestCorrectCrMemoIsAllowed(var PurchCrMemoHdr: Record "Purch. Cr. Memo Hdr.")
var //new line
IsHandled: Boolean; //new line
begin
IsHandled := false; //new line
OnBeforeTestCorrectCrMemoIsAllowed(PurchCrMemoHdr, IsHandled); //new line
if not IsHandled then begin //new line
TestIfPostingIsAllowed(PurchCrMemoHdr);
TestIfVendorIsBlocked(PurchCrMemoHdr, PurchCrMemoHdr."Buy-from Vendor No.");
TestIfVendorIsBlocked(PurchCrMemoHdr, PurchCrMemoHdr."Pay-to Vendor No.");
TestIfInvoiceIsCorrectedOnce(PurchCrMemoHdr);
TestIfCrMemoIsCorrectiveDoc(PurchCrMemoHdr);
TestVendorDimension(PurchCrMemoHdr, PurchCrMemoHdr."Pay-to Vendor No.");
TestDimensionOnHeader(PurchCrMemoHdr);
TestPurchLines(PurchCrMemoHdr);
TestIfAnyFreeNumberSeries(PurchCrMemoHdr);
TestExternalDocument(PurchCrMemoHdr);
TestInventoryPostingClosed(PurchCrMemoHdr);
end; //new line

OnAfterTestCorrectCrMemoIsAllowed(PurchCrMemoHdr);

end;

[IntegrationEvent(false, false)]
local procedure OnBeforeTestCorrectCrMemoIsAllowed(var PurchCrMemoHdr: Record "Purch. Cr. Memo Hdr.; var IsHandled: Boolean)
begin
end;

[github-actions]

Hi @krasivarna,

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:

• Specific title: Update the title so it identifies the exact procedure or event being requested, not just the codeunit.
• Alternatives considered: Explain which existing extensibility options or events in this flow were reviewed and why they are insufficient.
• IsHandled justification: Clarify why bypassing the standard validation logic with IsHandled is required instead of using a regular event.
• Performance considerations: Add a brief note about expected execution frequency and any performance impact.
• Data sensitivity review: Confirm whether this change exposes any sensitive data and whether that is acceptable.
• Multi-extension interaction: Describe how conflicts should be handled if multiple extensions subscribe and set IsHandled.

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.