Codeunit 5676 "Create Segment"
ContosoCoffeeDemoDataset · Microsoft.DemoData.CRM
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 6 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.CRM · BC29-30 · source at ea08af5e · facts from BC29
Procedures
IncreaseSaleSegment(): Code[20]EventSegment(): Code[20]WorkingPlaceSegment(): Code[20]
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 5209 “Create Customer” (5 calls:
OnRun → DomesticAdatumCorporation,OnRun → DomesticRelecloud,OnRun → DomesticTreyResearch, …) - Codeunit 5180 “Contoso CRM” (3 calls:
OnRun → FindContactNo,OnRun → InsertSegmentHeader,OnRun → InsertSegmentLine) - Codeunit 5385 “Create Interaction Template” (3 calls:
OnRun → Abstract,OnRun → Bus,OnRun → Golf) - Codeunit 5416 “Create Salesperson/Purchaser” (3 calls:
OnRun → BenjaminChiu,OnRun → HelenaRay,OnRun → OtisFalls) - Codeunit 5534 “Create Interaction Group” (1 call:
OnRun → Letter)
Called by
- Codeunit 5481 “CRM Module” (1 call:
CreateTransactionalData → (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 Segment"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.