Codeunit 6351 "PBI Deployment Events"

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

Events published

• OnReportDeployed(var Report: Interface "Power BI Uploadable Report"; DeployableReportType: Enum "Power BI Deployable Report") (integration)
  • subscribers: Codeunit 36959 “Power BI Subscribers” OnReportDeployed
• OnAfterDeleteAllDeploymentRecords(InCompany: Text[30]) (integration)
  • subscribers: Codeunit 36950 “Installation Handler” OnAfterDeleteAllDeploymentRecords

Event subscriptions

• ClearDeploymentRecordsOnEnvironmentCopy subscribes to Codeunit “Environment Cleanup” OnClearCompanyConfig

Procedures

• ClearDeploymentsForCompany(CompanyName: Text[30]) (internal): Wipes Power BI deployment tracking in the given company. Public entry point for out-of-module subscribers (BaseApp root) that need to react to events on objects the Power BI module can’t reference directly.

Called by

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 6350 “PBI Deployable Report Impl.” (1 call: FinalizeUpload → OnReportDeployed)
• Codeunit 8912 “Environment Cleanup Subs” (1 call: ClearPowerBIDeploymentsOnCopiedCompany → ClearDeploymentsForCompany)

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