Compare warehouse activity line bin

[SjorsVerschureLV]

Why do you need this change?

I would like to request this change to make it possible to pick from and to the same bin.

Describe the request

I would like to propose to replace the code below in table 5767 warehouse activity line, in the procedure checkinvalidbincode:

 if ("Location Code" = WarehouseActivityLine."Location Code") and
               ("Bin Code" = WarehouseActivityLine."Bin Code") and
               ("Unit of Measure Code" = WarehouseActivityLine."Unit of Measure Code")
            then
                Error(Text019, Format("Action Type"), Format(WarehouseActivityLine."Action Type"), Location.Code);

To replace it with a call to a new procedure below:

local procedure CompareWarehouseActivityLineBin(Rec, WarehouseActivityLine) 
var
    IsEqual: Boolean;
begin
    IsEqual := ("Location Code" = WarehouseActivityLine."Location Code") and
               ("Bin Code" = WarehouseActivityLine."Bin Code") and
               ("Unit of Measure Code" = WarehouseActivityLine."Unit of Measure Code");
    OnBeforeCompareWarehouseActivityLineBin(Rec, WarehouseActivityLine, IsEqual);
    if IsEqual then
        Error(Text019, Format("Action Type"), Format(WarehouseActivityLine."Action Type"), Location.Code);
end;

[IntegrationEvent(false, false)]
local procedure OnBeforeCompareWarehouseActivityLineBin(WarehouseActivityLine: Record "Warehouse Activity Line"; WarehouseActivityLine2: Record "Warehouse Activity Line";var IsEqual: Boolean)
    begin
    end;

[github-actions]

Hi @SjorsVerschureLV,

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:

• Title specificity: Update the title so it clearly identifies this as an event/extensibility request and names the target procedure/object precisely.
• Existing alternatives reviewed: Describe which existing events or alternative patterns were evaluated and why they are insufficient.
• Need for bypass-style extensibility: Explain why bypass-style extensibility is necessary instead of a regular event or redesign.
• Execution frequency / performance impact: Include the expected execution frequency and any performance impact considerations.
• Sensitive data exposure: Confirm whether any sensitive data exposure is involved.
• Extension interaction/conflicts: Explain potential interaction or conflicts when multiple extensions subscribe.

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.