Codeunit 6327 "Power BI Report Aggregator"

Base Application · System.Integration.PowerBI · BC28-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• LoadAllPending(Context: Text[50]): Boolean
• Next(var Report: Interface "Power BI Uploadable Report"): Boolean
• PendingCount(): Integer

Plus 5 local procedures.

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 6301 “Power BI Service Mgt.” (2 calls: GetPowerBIBlob → GetPowerBiTelemetryCategory, LoadOutOfTheBoxReports → GetPowerBiTelemetryCategory)
• Codeunit 6323 “Power BI System Table Report” (1 call: Next → SetBlobId)
• Codeunit 6326 “Power BI Customer Report” (1 call: Next → SetReportId)
• Codeunit 6350 “PBI Deployable Report Impl.” (1 call: Next → SetReport)

Called by

• Codeunit 6325 “Power BI Report Synchronizer” (4 calls: OnRun → LoadAllPending, OnRun → Next, OnRun → PendingCount, …)

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: "Power BI Report Aggregator"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.