Codeunit 3682 "BOM Tree"

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"): Adds a relation between two nodes connected in a parent- child relationship.
• TraverseDown(): Traverses the nodes starting from the root node and traverses down to the children and so on. Note that there can be many root nodes, in which case, the traversal starts from each of them.
• TraverseDown(Node: Codeunit "BOM Node"): Traverses the nodes starting from the given node and traverses down to the children and so on.
• ChildHasKey(ParentKey: Text; ChildKey: Text): Boolean: Finds if a node with the given key is a child of another node with the given parent key. The key of the parent node. The key of the child node. True if there was a child found with the key, false otherwise. This will return false if the node with the parent key was not found.

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 3683 “BOM Tree Impl.” (3 calls: AddRelation → AddRelation, ChildHasKey → ChildHasKey, TraverseDown → TraverseDown)

Called by

• Codeunit 3687 “Low-Level Code Calculator” (4 calls: AddChildToParent → AddRelation, AddChildToParent → ChildHasKey, PopulateFromBOMComponents → ChildHasKey, …)

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