Codeunit 6319 "Power BI Workspace Mgt."

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

Procedures

• GetMyWorkspaceLabel(): Text[200] Δ BC24
• GetTargetWorkspaceDisplayName(): Text[200] + BC29: Returns the name of the Power BI workspace that reports are deployed to for the current company.
• CheckTargetWorkspaceAllowsDeployment() + BC29
• GetWritableWorkspaces(var TempPowerBISelectionElement: Record "Power BI Selection Element" temporary) + BC29: Populates the buffer with the workspaces that deployable reports can be deployed to: the “My Workspace” option (represented by a null ID) plus every shared workspace the user can write to
• LookupTargetWorkspace(var WorkspaceId: Guid; var WorkspaceName: Text[200]): Boolean + BC29: Opens a lookup for the writable Power BI workspaces and returns the selected one. An empty (null) WorkspaceId means “My Workspace”.
• WorkspaceExists(WorkspaceId: Guid): Boolean + BC29: Returns true if the given workspace still exists and the user can write to it. An empty (null) WorkspaceId (“My Workspace”) is always considered valid.
• AddPersonalWorkspace(var TempPowerBISelectionElement: Record "Power BI Selection Element" temporary) Δ BC24
• AddSharedWorkspaces(var TempPowerBISelectionElement: Record "Power BI Selection Element" temporary) Δ BC24
• GetReportsAndWorkspaces(var TempPowerBISelectionElement: Record "Power BI Selection Element" temporary; EnglishContext: Text[30]) Δ BC24
• AddReportsForWorkspace(var TempPowerBISelectionElement: Record "Power BI Selection Element" temporary; WorkspaceID: Guid; WorkspaceName: Text[200]) + BC24 − BC24

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.” (7 calls: AddPersonalWorkspace → GetReportsUrl, AddReportsForWorkspace → CreateServiceProvider, AddReportsForWorkspace → GetPowerBiTelemetryCategory, …)
• Codeunit 6324 “Power BI Url Mgt” (1 call: GetReportsUrlForWorkspace → GetPowerBISharedReportsUrl)
• Page 6349 “Power BI Workspaces Lookup” (1 call: LookupTargetWorkspace → (object))

Called by

• Codeunit 104000 “Upgrade - BaseApp” (1 call: AddPowerBIWorkspaces → GetMyWorkspaceLabel)
• Codeunit 6323 “Power BI System Table Report” (1 call: FinalizeUpload → GetMyWorkspaceLabel)
• Codeunit 6325 “Power BI Report Synchronizer” (1 call: TargetWorkspaceIsValid → WorkspaceExists)
• Codeunit 6349 “PBI Deploy. Upload Tracker” (1 call: SetTargetWorkspace → GetTargetWorkspaceDisplayName)
• Page 1 “Company Information” (1 call: UpdatePowerBIWorkspaceDisplayName → GetTargetWorkspaceDisplayName)
• Page 6322 “Power BI WS Report Selection” (1 call: TryLoadReportsList → GetReportsAndWorkspaces)
• Page 6349 “Power BI Workspaces Lookup” (1 call: Initialize → GetWritableWorkspaces)

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