Hi @hi_world ,
Thanks for reaching out to us with your problem. The CI/CD solution provided by pbi-tools with Git in Power BI is generally seen as a significant advancement in Power BI development. It allows for version control of reports and datasets, and the use of Azure DevOps to deploy them to Service. Here are some advantages and potential drawbacks of this solution:
Advantages:
Version control: Git allows for version control of Power BI files, making it easier to track changes and collaborate with others.
Automated deployment: CI/CD pipelines can be set up to automatically deploy changes to Power BI reports and dashboards.
Automated Quality Checks: The CI/CD pipelines process the PBIP metadata files and apply a series of quality checks to your development before deploying it to the production system. By implementing automated quality tests, you can prevent common mistakes, and enhance team efficiency.
Azure DevOps build pipeline integration with Power BI Desktop projects - Power BI | Microsoft Learn
Fabric Power BI CI/CD with Azure DevOps | Liesel's Tech Ramblings Blog (lieselhughes.com)
PowerBI - CICD using Azure DevOps - Microsoft Fabric Community
Potential Drawbacks:
Complexity: Setting up and maintaining the CI/CD pipelines might require a certain level of technical expertise.
Limitations with Certain Data Sources: Updating parameters using Power BI REST API doesn’t support for the data sources like SQL, Oracle, Teradata.
Infrastructure requirements: The solution may require additional infrastructure, such as a Git repository and a CI/CD pipeline, which may increase costs.
Reliability: It largely depends on the specific implementation and the complexity of the Power BI reports and datasets being used. However, the integration of Power BI with Azure DevOps has been positively received in the community. As with any tool, it’s recommended to thoroughly test in your environment to ensure it meets your needs.
Best Regards
