pageManufacturingofficial - Microsoftderived - from the source, no model text

Page 99000836 "Routing Personnel"

Base Application · Microsoft.Manufacturing.Routing

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Table 99000803 "Routing Personnel" (relates to)Routing PersonnelPage 99000765 "Routing Lines" (calls)Routing LinesPage 99000767 "Routing Version Lines" (calls)Routing Version LinesCreate routings (Learn pages)Create routings

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

Properties

Property Value
Caption Routing Personnel
SourceTable Routing Personnel
PageType List

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
Control1 No. No. Specifies the number of the involved entry or record, according to the specified number series. from the table field
Description Description Specifies the description of the personnel, such as the names or the professions. from the table field

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.

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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

Evidence 2 sources