codeunit 76 "Purch.-Get Drop Shpt."

[DanielSmutek]

Why do you need this change?

We need this event to implement customer functionality

Describe the request

Can you please add event to codeunit 76 "Purch.-Get Drop Shpt."

local procedure "Code"()
var
    PurchLine2: Record "Purchase Line";
    IsHandled: Boolean;
begin
    PurchHeader.TestField("Document Type", PurchHeader."Document Type"::Order);

    if PurchHeader."Sell-to Customer No." = '' then
        Error(SelltoCustomerBlankErr);

    IsHandled := false;
    OnCodeOnBeforeSelectSalesHeader(PurchHeader, SalesHeader, IsHandled);
    if not IsHandled then begin
        SalesHeader.SetCurrentKey("Document Type", "Sell-to Customer No.");
        SalesHeader.SetRange("Document Type", SalesHeader."Document Type"::Order);
        SalesHeader.SetRange("Sell-to Customer No.", PurchHeader."Sell-to Customer No.");
        if (PAGE.RunModal(PAGE::"Sales List", SalesHeader) <> ACTION::LookupOK) or
           (SalesHeader."No." = '')
        then
            exit;
    end;

    PurchHeader.LockTable();
    // NEW EVENT >>
    OnCodeOnBeforeTestFieldDocuments(PurchHeader, SalesHeader, IsHandled);
    if not IsHandled then begin
    // NEW EVENT <<
    SalesHeader.TestField("Document Type", SalesHeader."Document Type"::Order);
    PurchHeader.TestField("Sell-to Customer No.", SalesHeader."Sell-to Customer No.");
    PurchHeader.TestField("Ship-to Code", SalesHeader."Ship-to Code");
    // NEW EVENT >>
    end;
    // NEW EVENT <<
    if PurchHeader.DropShptOrderExists(SalesHeader) then
        PurchHeader.AddShipToAddress(SalesHeader, true);


// NEW EVENT >>
local procedure OnCodeOnBeforeTestFieldDocuments(var PurchaseHeader: Record "Purchase Header"; var SalesHeader: Record "Sales Header"; var IsHandled: Boolean)
begin
end;
// NEW EVENT <<

[github-actions]

Hi @DanielSmutek,

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:

• Clear issue title: Update the title so it clearly identifies this as an event request and describes the specific change.
• Scenario and limitation details: Describe the current limitation and the overall business/technical scenario in more concrete terms.
• Concrete justification: Explain the technical or business need beyond a generic statement that customer functionality is required.
• Alternatives evaluated: Specify which existing events or extension points were considered and why they are not sufficient.
• Why IsHandled is required: Explain why an IsHandled pattern is necessary for this scenario.
• Performance impact: Describe the expected execution frequency and any performance considerations.
• Sensitive data considerations: Clarify whether the change could expose any sensitive data.
• Extension conflict handling: Explain how conflicts with other subscribing extensions should be handled.

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.