Codeunit 5698 "Create Posted Analytics Data"

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

Events published

• OnBeforePostPurchaseOrdersForAnalytics() (integration)
• OnAfterPostPurchaseOrdersForAnalytics() (integration)

Procedures

• PostSalesInvoicesForAnalytics()
• PostPurchaseOrdersForAnalytics()

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 5688 “Create Extended Purch Document” (1 call: PostPurchaseOrdersForAnalytics → AnalyticsReference)
• Codeunit 5692 “Create Extended Sales Document” (1 call: PostSalesInvoicesForAnalytics → AnalyticsReference)
• Codeunit 80 “Sales-Post” (1 call: PostSalesInvoicesForAnalytics → (object))
• Codeunit 90 “Purch.-Post” (1 call: PostPurchaseOrdersForAnalytics → (object))

Called by

• Codeunit 5687 “Analytics Module” (1 call: CreateHistoricalData → (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 Posted Analytics Data"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.