Codeunit 3683 "BOM Tree Impl."

Base Application · Microsoft.Inventory.BOM.Tree · BC23-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• AddRelation(Parent: Codeunit "BOM Node"; Child: Codeunit "BOM Node")
• TraverseDown()
• TraverseDown(NodeContent: Codeunit "BOM Node")
• ChildHasKey(ParentKey: Text; ChildKey: Text): Boolean

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.

• Codeunit 3675 “BOM Tree Node Dictionary” (6 calls: AddRelation → Add, AddRelation → TryGet, ChildHasKey → TryGet, …)
• Codeunit 3684 “BOM Tree Node” (5 calls: AddRelation → AddChild, AddRelation → Create, ChildHasKey → IsChild, …)
• Codeunit 3688 “BOM Node” (1 call: AddRelation → GetKey)

Called by

• Codeunit 3682 “BOM Tree” (3 calls: AddRelation → AddRelation, ChildHasKey → ChildHasKey, TraverseDown → TraverseDown)

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: "codeunit", object_name: "BOM Tree Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.