Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
Hi, we have serveral premium per user workspaces which are synced to folders a GIT Azure DevOps repository. These workspaces all contain a mix of Power BI reports, Semantic Models and Power BI Paginated reports (.rdl files). In one of the workspaces all paginated reports all now say "Unsupported" as the GIT status without any change to them or the workspace. This is not the case in the other workspaces. Has anyone else ran into this issue?
I am having the same issue. Checked an RDL file into a git repository that is synced to a power bi workspace... but it doesn't appear in the workspace after refreshing source countrol in the PBI service. Other content (ie, power bi reports) work fine.
Yepp, having the same issue here. Pushed rdl files from local repo to git directly without publishing to service first. Under source control they don't show up no matter how many times I hit refresh. Interestingly enough in one of our test workspaces, even some native power bi reports are showing up as unsupported.
I am also facing the same issue however few workspaces are looking good but a few workspaces are showing the same issue.
When I add a new paginated report in the workspace, it is properly committed using the source control but it is not showing as Sync in Git Status column.
Hi @dilipsahu ,
You can follow the above steps to troubleshoot one by one, if it is still not resolved, please provide information about the configuration of your git, and you can refer to the above documentation on the inability to synchronize the workspace to re-upload synchronization
Best regards,
Albert He
Hi @Alpine_ ,
Based on your description, there are several things you can do to check for problems:
1. Make sure that your Git repository settings have not changed. Specifically, check to see if the `.rdl` file extension is still supported, and if there have been any recent updates to the Git settings that might affect these files.
2. Make sure your Git repository settings have not changed. Specifically, check to see if the `.rdl` file extension is still supported, and if there have been any recent updates to your Git settings that might affect these files.
3. Look at the commit history to see if there have been any recent changes that affected Git's interaction with `.rdl` files. It's possible that changes to the repository or workspace configuration may have inadvertently caused this problem.
You can check out this official document for more details on GIT integration with paged reports
Git integration with paginated reports - Power BI | Microsoft Learn
Best regards,
Albert He
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Do you recall making any changes to these rdl's ?
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
There was no changes in the rdls, workspaces, or repo whent his happened. I have opened a ticket with microsoft. I will post the resolution here when I know.
Any luck in resolving this issue? I still cannot get the Power BI service to pull rdl files from git. PBIP files are working fine.
No real resolution. The feature just started working again. We've moved away from using the git integration feature due to the buggy-ness. And instead just use powershell scripts to deploy eerything from Azure Dev Ops pipelines. Here is a sample function I use for deploying paginated reports.
Function Import-PaginatedReport {
<#
.SYNOPSIS
Used to import a paginated report (Rdl file extension) to a Power BI Service workspace.
.OUTPUTS
Retruns the import process id
.NOTES
Must be ran in a sesssion where a properly permissioned Service Principle has an open connection to Power BI service.
#>
param(
[Parameter(Mandatory,
HelpMessage = "Authentication bearer API token for power BI Service API. In format: `"Bearer...`" ")]
[string]
$PBIAuthToken,
[Parameter(Mandatory,
HelpMessage = "File Information of the paginated report (rdl file) to import.")]
[System.IO.FileSystemInfo]
$RdlFile,
[Parameter(Mandatory,
HelpMessage = "The name of the paginated report to import.")]
[String]
$ReportName,
[Parameter(Mandatory,
HelpMessage = "The guid id of the Power BI workspace to import the report to.")]
[string]
$WorkspaceId
)
BEGIN{
# Create Templates for Form and URI
$FormTemplate = @'
--{0}
Content-Disposition: form-data; name="{1}"; filename="{1}"
Content-Type: application/rdl
{3}
--{0}--
'@
$UriTemplate = "https://api.powerbi.com/v1.0/myorg/groups/{0}/imports?datasetDisplayName={1}&nameConflict={2}"
$enc = [System.Text.Encoding]::GetEncoding("utf-8")
$headers = Get-PowerBIAccessToken
$Report = Get-PowerBIReport -Name $ReportName -WorkspaceId $WorkspaceId
if($null -eq $Report){
# If report does not exist then use Abort conflict handle mode
$NameConflictMode = "Abort"
}
# If report with name already exist check if paginated report
else{
$ReportInfo = Get-ReportById -PBIAuthToken $PBIAuthToken -ReportId $Report.Id -WorkspaceId $WorkspaceId
$ReportType = $ReportInfo.ReportType
# If report type is a paginated report then use Overwrite conflict mode
if($ReportType -eq "PaginatedReport"){
$NameConflictMode = "Overwrite"
}
# if non paginated report of the same name exists use abort conflict mode
else{
$NameConflictMode = "Abort"
}
}
}
PROCESS{
$Result = $False
$boundary = [guid]::NewGuid().Guid
$bytes = [System.IO.File]::ReadAllBytes($RdlFile.FullName)
$Data = $enc.GetString($bytes)
$uri = $UriTemplate -f $WorkspaceId, $RdlFile.Name, $NameConflictMode
$body = $FormTemplate -f $boundary, $ReportName, $ContentType, $Data
$FormContentType = "multipart/form-data; boundary=$boundary"
Try {
$Result = Invoke-RestMethod -Uri $uri -Method POST -Headers $headers -ContentType $FormContentType -Body $body -WebSession $STWebSession -DisableKeepAlive
} Catch {
Write-Error $_
}
return $Result.id
}
END{}
}