pageInventoryofficial - Microsoftderived - from the source, no model text

Page 5747 "Transfer Routes"

Base Application · Microsoft.Inventory.Transfer

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 14 "Location" (relates to)LocationCodeunit 9200 "Matrix Management" (calls)Matrix ManagementTable 5430 "Planning Error Log" (calls)Planning Error Log

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 · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Transfer Routes
SourceTable Location
PageType Card
UsageCategory Administration
ApplicationArea Location

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
Options Show Show Specifies if the selected value is shown in the window.
Show Transfer-to Name ShowTransferToName Specifies that the name of the transfer-to location is shown on the routing.
Column Set MATRIX_CaptionRange Specifies the range of values that are displayed in the matrix window, for example, the total period. To change the contents of the field, choose Next Set or Previous Set.
Content MatrixForm part Page 9285 “Transfer Routes Matrix” —

Actions

Group Action ToolTip Runs
Processing Previous Set Go to the previous set of data.
Next Set Go to the next set of data.

Procedures

3 local procedures, no public ones.

Triggers

OnOpenPage

Relations

Calls

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.

Called by

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 Routes"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources