Codeunit 6349 "PBI Deploy. Upload Tracker"
Base Application · System.Integration.PowerBI
Across versions
- BC23-27not present
- BC28added
- BC291 procedures added
- BC30unchanged
Neighbourhood 2 connected objects and pages
Base Application · System.Integration.PowerBI · BC28-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
Load(ReportKey: Text[100])Reset()GetStatus(): Enum "Power BI Upload Status"TransitionTo(NewStatus: Enum "Power BI Upload Status")Fail(ErrorMessage: Text; ErrorCallStack: Text)SetImportId(ImportId: Guid)GetImportId(): GuidSetImportResult(UploadedReportId: Guid; EmbedUrl: Text[2048]; DatasetId: Text)SetUploadedReportName(ReportName: Text)SetTargetWorkspace(WorkspaceId: Guid)+ BC29GetUploadedReportName(): TextGetUploadedReportId(): GuidGetEmbedUrl(): Text[2048]GetDatasetId(): TextShouldOverwrite(IncomingReportVersion: Integer): BooleanScheduleRetry(RetryAfter: DateTime)HasScheduledRetry(): BooleanSave()GetDeployableReportFromReportKey(ReportKey: Text[100]; var DeployableReportType: Enum "Power BI Deployable Report")(internal)
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:
Save → GetPowerBiTelemetryCategory,TransitionTo → GetPowerBiTelemetryCategory) - Codeunit 6319 “Power BI Workspace Mgt.” (1 call:
SetTargetWorkspace → GetTargetWorkspaceDisplayName)
Implements
Recent changes
- 2026-10-05 #12242 29.x: Removing the restriction of deploying Power BI reports only to evaluation companies (releases/29.x, BC29, feature)
- 2026-10-02 #12189 Removing the restriction of deploying Power BI reports only to evaluation companies (main, BC30, feature)
- 2026-09-10 #10348 Adding a Power BI workspace to Company Information to be used when deploying reports (main, BC30, feature)
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 Deploy. Upload Tracker"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.