pageInventoryofficial - Microsoftderived - from the source, no model text

Page 5748 "Transfer Route Specification"

Base Application · Microsoft.Inventory.Transfer

Across versions

  1. BC23-28present
  2. BC29declaration changed
  3. BC30unchanged

Neighbourhood 2 connected objects and pages

Table 5742 "Transfer Route" (relates to)Transfer RoutePage 9285 "Transfer Routes Matrix" (calls)Transfer Routes Matrix

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Inventory.Transfer · captioned “Trans. Route Spec.” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Trans. Route Spec.
SourceTable Transfer Route
PageType Card

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
General In-Transit Code In-Transit Code Specifies the in-transit code for the transfer order, such as a shipping agent. from the table field
Shipping Agent Code Shipping Agent Code Specifies the code for the shipping agent who is transporting the items. from the table field
Shipping Agent Service Code Shipping Agent Service Code Specifies the code for the service, such as a one-day delivery, that is offered by the shipping agent. from the table field
Direct Transfer Direct Transfer Specifies whether the transfer order is a direct transfer. Direct transfers move inventory directly between locations without using an in-transit location. from the table field
Direct Transfer Posting Direct Transfer Posting Specifies the posting type for direct transfer. from the table field

Events published

  • OnBeforeClosePage(TransferRoute: Record "Transfer Route"; var CanBeDeleted: Boolean) (integration)

Triggers

OnClosePage, OnInit, OnAfterGetCurrRecord

Relations

Called by

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Transfer Route Specification"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources