Codeunit 5305 "Create Territory"
ContosoCoffeeDemoDataset · Microsoft.DemoData.Inventory
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 4 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.Inventory · BC29-30 · source at ea08af5e · facts from BC29
Procedures
East(): Code[10]EastAnglia(): Code[10]Foreign(): Code[10]London(): Code[10]Midlands(): Code[10]North(): Code[10]NorthEast(): Code[10]NorthWest(): Code[10]NorthWales(): Code[10]South(): Code[10]Scotland(): Code[10]SouthEast(): Code[10]SouthWest(): Code[10]SouthWales(): Code[10]West(): Code[10]
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 5180 “Contoso CRM” (1 call:
OnRun → InsertTerritory)
Called by
- Codeunit 5209 “Create Customer” (1 call:
OnRun → Foreign) - Codeunit 5539 “Create Vendor” (1 call:
OnRun → Foreign) - Codeunit 5680 “Inventory Module” (1 call:
CreateSetupData → (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 Territory"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.