Codeunit 4794 "Create Svc Fault"
ContosoCoffeeDemoDataset · Microsoft.DemoData.Service
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.Service · BC29-30 · source at ea08af5e · facts from BC29
Procedures
ErrorSymptom(): Code[10]LeakingSymptom(): Code[10]NoiseSymptom(): Code[10]DefaultTroubleShootingCode(): Code[20]
Plus 5 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 5125 “Contoso Service” (7 calls:
CreateFaultCodes → InsertFaultCode,CreateFaultResolutionRelations → InsertFaultResolutionRelation,CreateResolution → InsertResolution, …) - Codeunit 5103 “Create Svc Setup” (2 calls:
CreateFaultResolutionRelations → DefaultServiceItemGroup,CreateTroubleshooting → DefaultServiceItemGroup)
Called by
- Codeunit 5151 “Service 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 Svc Fault"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.