Codeunit 5463 "Create Dimension"

ContosoCoffeeDemoDataset · Microsoft.DemoData.Finance · BC29-30 · source at ea08af5e · facts from BC29

Procedures

• AreaDimension(): Code[20]
• BusinessGroupDimension(): Code[20]
• CustomerGroupDimension(): Code[20]
• DepartmentDimension(): Code[20]
• SalesCampaignDimension(): Code[20]

Plus 1 local procedures.

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 5494 “Contoso Dimension” (1 call: OnRun → InsertDimension)

Called by

• Codeunit 5417 “Create Dimension Value” (5 calls: OnRun → AreaDimension, OnRun → BusinessGroupDimension, OnRun → CustomerGroupDimension, …)
• Codeunit 5663 “Create Purchase Dim. Value” (4 calls: OnRun → AreaDimension, OnRun → BusinessGroupDimension, OnRun → DepartmentDimension, …)
• Codeunit 5412 “Create Sales Dimension Value” (3 calls: OnRun → AreaDimension, OnRun → BusinessGroupDimension, OnRun → CustomerGroupDimension)
• Codeunit 5536 “Create Analysis View” (3 calls: OnRun → AreaDimension, OnRun → CustomerGroupDimension, OnRun → DepartmentDimension)
• Codeunit 5415 “Finance Module” (1 call: CreateMasterData → (object))
• Codeunit 5614 “Create FA Dimension Value” (1 call: OnRun → DepartmentDimension)

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