Codeunit 5296 "EService Module"

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

Procedures

• RunConfigurationPage()
• GetDependencies(): List of [enum "Contoso Demo Data Module"]
• CreateSetupData()
• CreateMasterData()
• CreateTransactionalData()
• CreateHistoricalData()

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 5231 “Create Incoming Document” (1 call: CreateTransactionalData → (object))
• Codeunit 5232 “Create Incoming Document Setup” (1 call: CreateSetupData → (object))
• Codeunit 5236 “Create Online Map Setup” (1 call: CreateSetupData → (object))
• Codeunit 5300 “Create Online Map Para. Setup” (1 call: CreateSetupData → (object))
• Page 5296 “EService Demo Data Setup” (1 call: RunConfigurationPage → (object))

Implements

• Enum 5160 “Contoso Demo Data Module”

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