Page 903 "Assembly Lines"

Base Application · Microsoft.Assembly.Document · BC23-30 · source at ea08af5e · facts from BC29

Properties

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).

Actions

Relations

• source table Table 901 “Assembly Line”

Pages and codeunits on this table

• Table 901 “Assembly Line” (drill-down page)
• Table 901 “Assembly Line” (lookup page)

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.

• Codeunit 5997 “Assembly Warehouse Mgt.” (2 calls: OnShowSourceDocLine → (object), ShowAssemblyLine → (object))
• Codeunit 926 “Assembly Line-Reserve” (2 calls: OnLookupLine → (object), ShowSourceLines → (object))

Documented on Microsoft Learn

• Assembly Management
• Understanding Assemble to Order and Assemble to Stock
• Assemble Items
• Create Blanket Assembly Orders
• Quote an Assemble-to-Order Sale
• Sell Assemble-to-Order Items and Inventory Items Together
• Sell Inventory Items in Assemble-to-Order Flows
• Sell Items Assembled to Order
• Undo Assembly Posting
• Assembly Reports and Analytics in Business Central

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