...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Excerpt |
|---|
Code to be executed prior to posting via standard posting routines. When migrating code from older MOB versions, this event is the most direct 1:1 comparison to existing in-line customizations. |
Template
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnBeforePostAnyOrder', '', true, true)]
procedure OnPostReceiveOrder_OnBeforePostAnyOrder(var _OrderValues: Record "MOB Common Element"; var _RecRef: RecordRef)
begin
end;
Description
The event is mostly used to validate collected "header" level steps (added from OnGetReceiveOrderLines_OnAddStepsToAnyHeader) and to write collected header level steps values to fields in the database that subsequently can be accessed from standard posting function events.
...
Use this event to
| Excerpt |
|---|
Handle collected values from Header Steps for any of four different Receive Order sources. Parameters includes a RecRef-instance for the header table. |
Description
This event is used to handle collected "header" level steps and is executed only once per order posting from the mobile device.
Like other "Any"-events, this event is executed for all four different receive document sources (:
- Warehouse Receipt
...
- Purchase Order
...
- Transfer Order
...
- Sales Return Order
...
If you are implementing changes for a specific document source , you likely - including if you need to set arguments in standard BC posting routines prior to posting - you should use one of the document-source-specific events (see "This event is executed afterafterwards", below).Steps added at .
Examples of use could be:
- Stage collected values to new or existing fields in the database that can subsequently can be accessed from standard posting function events.
- Validate collected values against live data since registration at the mobile device is mostly conducted offline.
- But not to process "line" level
...
- steps. Steps added via OnAddStepsToAnyLine[...] is better handled via OnPostReceiveOrder_OnHandleRegistrationFor...
...
- -events.
This event is executed after each of these following events:
OnPostReceiveOrder_OnBeforePostWarehouseReceiptOnPostReceiveOrder_OnBeforePostPurchaseOrderOnPostReceiveOrder_OnBeforePostTransferOrderOnPostReceiveOrder_OnBeforePostSalesReturnOrder
When is data committed
| Note | ||
|---|---|---|
| ||
Database transactions in [...]OnBeforePostAnyOrderthis event is committed to database prior to calling standard BC posting functionroutines. sYour customized code must be structured accordingly. You may Nearly always you must subscribe to standard BC posting events to do your actual processing to ensure rollback of your database transactions or trigger events on-after posting, if this is required for your codeon error. Note: Standard posting functions includes several unconditional commits in standard code. If When you need to rely on standard code rollback for your custom code, this needs to be taken into account and the standard integration event you are subscribing to needs to must be selected carefully. |
Event is executed after each of these following events:
OnPostReceiveOrder_OnBeforePostWarehouseReceipt
OnPostReceiveOrder_OnBeforePostPurchaseOrder
OnPostReceiveOrder_OnBeforePostTransferOrder
OnPostReceiveOrder_OnBeforePostSalesReturnOrder
...
Template
[EventSubscriber(ObjectType::Codeunit, Codeunit::"MOB WMS Receive", 'OnPostReceiveOrder_OnBeforePostAnyOrder', '', true, true)]
local procedure OnPostReceiveOrder_OnBeforePostAnyOrder(var _OrderValues: Record "MOB Common Element"; var _RecRef: RecordRef)
begin
// Add your custom code here...
// Note: OnBeforePost-events is committed to the database prior to posting. Your custom code must be structured accordingly (or use standard BC events).
end;
| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...