Table 6316 "Power BI Deployment"
Base Application · System.Integration.PowerBI
Across versions
- BC23-27not present
- BC28added
- BC295 procedures added, 2 fields added
- BC30unchanged
Neighbourhood 1 connected objects and pages
Base Application · System.Integration.PowerBI · BC28-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Power BI Deployment |
| Access | Public |
| DataClassification | SystemMetadata |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Report Id | Enum “Power BI Deployable Report” | — | enum Enum 6316 “Power BI Deployable Report” |
| 2 | Import ID | Guid | — | |
| 3 | Uploaded Report ID | Guid | — | |
| 4 | Report Embed Url | Text[2048] | — | |
| 5 | Dataset Id | Text[200] | — | |
| 6 | Deployed Version | Integer | — | |
| 7 | Retry After | DateTime | — | |
| 8 | Uploaded Report Name | Text[200] | — | |
| 9 | Power BI Workspace Id + BC29 | Guid | — | |
| 10 | Deployed Workspace Name + BC29 | Text[200] | — | DataClassification CustomerContent |
Keys
- PK: Report Id (clustered)
Procedures
GetLatestStateRecord(var PowerBIDeploymentState: Record "Power BI Deployment State"): Boolean: Retrieves the latest deployment state record. Returns false if none exists.GetLatestCompletedState(): Record "Power BI Deployment State": Retrieves the latest completed deployment state record. Returns an empty record if there’s noneGetUploadStatus(): Enum "Power BI Upload Status": Derives the current upload status from the latest Power BI Deployment State record. This is the single source of truth for deployment status.FailCurrentStep(FailedReason: Text; FailedCallstack: Text): Marks the latest state record as failed with the given reason. If no state record exists yet (e.g. the very first step failed before any transition), creates one with Status Reached = NotStarted so the failure is never silently lost.ResetDeployment(): Resets a deployment by deleting all state records. After this, GetUploadStatus() returns NotStarted and the aggregator will include the report as pending work for re-deployment. Used both for retrying failed deployments and for applying version updates.GetDeploymentStatus(): Enum "Power BI Deployment Status"+ BC29GetDeploymentOutcome(DeploymentStatus: Enum "Power BI Deployment Status"): Enum "Power BI Deployment Outcome"+ BC29QueueForDeployment(ReportId: Enum "Power BI Deployable Report")+ BC29 (internal)DeleteAllRecords(): Wipes all local deployment tracking data for the current company across every deployable report. Reports already uploaded to the Power BI workspace are not touched.DeleteAllRecords(InCompany: Text[30]): Wipes all local deployment tracking data in the specified company. Used by subscribers that need to clear records in a different company than the caller’s (e.g. after Copy Company, where the subscriber runs in the source company but must wipe the target).RecordStep(NewStatus: Enum "Power BI Upload Status"): Creates a new state record for the given status.
Plus 2 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.” (1 call:
FailCurrentStep → GetPowerBiTelemetryCategory)
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: "table", object_name: "Power BI Deployment"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.