Codeunit 5451 "Create Campaign Status"
ContosoCoffeeDemoDataset · Microsoft.DemoData.CRM
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.CRM · BC29-30 · source at ea08af5e · facts from BC29
Procedures
Planned(): Code[10]Approved(): Code[10]Initiated(): Code[10]Scheduled(): Code[10]Started(): Code[10]Done(): 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 → InsertCampaignStatus)
Called by
- Codeunit 5442 “Create Campaign” (2 calls:
OnRun → Done,OnRun → Started) - Codeunit 5481 “CRM 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 Campaign Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.