Page 99000835 "Routing Tools"
Base Application · Microsoft.Manufacturing.Routing
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Manufacturing.Routing · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Routing Tools |
| SourceTable | Routing Tool |
| 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 a description for the routing tool. from the table field |
Relations
- source table Table 99000802 “Routing Tool”
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.
- Page 99000765 “Routing Lines” (1 call:
ShowTools → (object)) - Page 99000767 “Routing Version Lines” (1 call:
ShowTools → (object))
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 Tools"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.