Use this event to
Add filter conditions for Sales Headers that cannot be solved by OnSetFilter-event.
Description
This event is triggered after filters have been applied to the Sales Header. The event should be used only when it is not possible to use OnSetFilter-event to solve if the Header should be included in the OrderList response.
The Sales Order can be excluded from the OrderList response by setting the parameter _IncludeInOrderList to false.
Learn about Basic vs. Complex filtering
Template
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Pick", 'OnGetPickOrders_OnIncludeSalesHeader', '', true, true)]
local procedure OnGetPickOrders_OnIncludeSalesHeader(_SalesHeader: Record "Sales Header"; var _HeaderFilters: Record "MOB NS Request Element"; var _HeaderFilters: Record "MOB NS Request Element"; var _IncludeInOrderList: Boolean)
begin
end;
Example
// [Example]: Do not include in order list if customer is blocked
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Pick", 'OnGetPickOrders_OnIncludeSalesHeader', '', true, true)]
local procedure MyOnGetPickOrders_OnIncludeSalesHeader(_SalesHeader: Record "Sales Header"; var _HeaderFilters: Record "MOB NS Request Element"; var _HeaderFilters: Record "MOB NS Request Element"; var _IncludeInOrderList: Boolean)
var
Customer: Record Customer;
begin
if Customer.get(_SalesHeader."Sell-to Customer No.") and (Customer.Blocked <> Customer.Blocked::" ") then
_IncludeInOrderList := false;
end;
More examples
-
Case: Filter Receipts based on Comments — The user wants to filter Receipts on whether they have comments or not
-
How-to: Filter Orders - Complex — Examples for including/excluding orders using complex per-document filtering
Version History
Version | Changes |
---|---|
MOB5.13 | Introduced |