Codeunit 5663 "Create Purchase Dim. Value"
ContosoCoffeeDemoDataset · Microsoft.DemoData.Purchases
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 5 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.Purchases · BC29-30 · source at ea08af5e · facts from BC29
Triggers
OnRun
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 5417 “Create Dimension Value” (7 calls:
OnRun → AmericaNorthArea,OnRun → EuropeNorthEUArea,OnRun → EuropeNorthNonEUArea, …) - Codeunit 5539 “Create Vendor” (5 calls:
OnRun → DomesticFirstUp,OnRun → DomesticNodPublisher,OnRun → DomesticWorldImporter, …) - Codeunit 5463 “Create Dimension” (4 calls:
OnRun → AreaDimension,OnRun → BusinessGroupDimension,OnRun → DepartmentDimension, …) - Codeunit 5494 “Contoso Dimension” (1 call:
OnRun → InsertDefaultDimensionValue)
Called by
- Codeunit 5394 “Purchase Module” (1 call:
CreateMasterData → (object))
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: "Create Purchase Dim. Value"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.