Pieplines dont suport deploying PBIP so I need to Revert from PBIR to PBIR_Legacy

[erikmi]

I’m currently facing an issue where Deployment Pipelines do not support deploying PBIP, forcing me to revert reports from PBIR to PBIR_Legacy. Unfortunately, there’s no official method to switch from PBIR back to PBIR_Legacy.

Has anyone discovered a workaround—either a way to deploy reports in the new PBIR format through pipelines or to revert them to the legacy format? Any guidance or suggestions would be greatly appreciated.

[V-yubandi-msft]

Hi @erikmi ,

Thank you for reaching out to Microsoft Fabric Support.

We confirm that the solution provided by @ibarrau  is accurate and should effectively address the issue you are facing. Their suggestion to combine Git repositories with Fabric API requests to update changes in the workspace is a smart workaround, following best practices for version control and deployment in modern data environments.

This solution not only resolves the immediate issue but also establishes a robust workflow for future deployments. If you need any help with Git integration or Fabric API requests, feel free to ask.

If the issue has been resolved, please mark it as the Accepted Solution to help others.

[Martin_D]

Hi,
According to the Microsoft documentation the scenario described by @erikmi is a valid and supported scenario. This scenario can only work if PBIP format is compatible with replacing data sources using deployment rules in Fabric deployment pipelines. That's exactly the purpose of this scenario.

Link to the Microsoft documentation, option #3: CI/CD workflow options in Fabric - Microsoft Fabric | Microsoft Learn

Quote:

When should you consider using option #3?

[...] 

• When deployment rules, autobinding and other available APIs are sufficient to manage the configurations between the stages of the release pipeline.

If this does not work I would treat this as bug from Microsoft.

Kind regards,

Martin

[ibarrau]

Hi. How about fabric git integration. Once the changes are at the repo, you can use a Fabric API git request to update changes at the workspace. That would be like the deploy you are looking for. Working with git repos.

You can keep this doc as reference to keep track of the limitation of pbir and deployment pipelines: https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-report#pbir-considerations-an...

I hope that helps,

[erikmi]

I have the following setup: I have separate DEV, TEST, and PROD workspaces for my report. The DEV workspace is synced with Git/DevOps. I want to use deployment pipelines to deploy from DEV to TEST and from TEST to PROD. However, while deploying, I need to use deployment rules to automatically switch the connection strings to the corresponding test or production data sources. Unfortunately, using DevOps pipelines isn't a viable option for this, as it does not support automatic changes to connection strings in the same way deployment rules do.

If you have any other ideas or suggestions, I would be really grateful.

[ibarrau]

Hi. Deployment pipelines is not an option because it has the limitation I have mentioned before. At devops you can do almost anything. When running the deploy or pull request between branches you can run things at the pipeline, things like powershell or python code. In there you can request the git update for syncing the workspace with the branch, then update datasource settings (or even better if you have created the sources with parameters then update parameters) with the Power Bi Rest API.
The credentials might be tricky, there is an update connection api request at Fabric API that is very new, but you could just do it manually the first time and then it will be saved unless you add a new source.

I hope that make sense