Codeunit 5308 "Contoso Data Exchange"
ContosoCoffeeDemoDataset · Microsoft.DemoTool.Helpers
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoTool.Helpers · BC29-30 · source at ea08af5e · facts from BC29
Procedures
ImportDataExchangeDefinition(FileName: Text)InsertDataExchangeType(Code: Code[20]; Description: Text[250]; DataExchangeDefinitionCode: Code[20])UpdateSEPACAMT05300108DataExchDefLabels()
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 104000 “Upgrade - BaseApp” (1 call:
UpdateSEPACAMT05300108DataExchDefLabels → UpdateSEPACAMT05300108DataExchDefLabels)
Called by
- Codeunit 5307 “Create Data Exchange” (2 calls:
OnRun → ImportDataExchangeDefinition,OnRun → UpdateSEPACAMT05300108DataExchDefLabels) - Codeunit 5309 “Create Data Exchange Type” (1 call:
OnRun → InsertDataExchangeType)
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: "Contoso Data Exchange"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.