Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hi folks,
I'm facing a interesting issue between Azure Repo (GIT) and commits and I want to share with you.
I have workspace connected to Azure DevOps Repo and that works fine, meaning, I am able to insert/update reports.Also, I've created Power BI pipeline for managing my deployments and only one workspace (dev) has connected to GIT.
However, case I try to revert any commit (rollback changes), Power BI pipeline show up a difference for reports only.
DevOps
Sync status OK
Pipeline status
Does someone know what's wrong?
Solved! Go to Solution.
Hi @Johonnatan ,
I suggest you to refer to this blog to learn more details: Compare content in different stages before deployment - Microsoft Fabric | Microsoft Learn.
Different – An item that exists both in the source and the target stage, where one of the versions was changed after the last deployment. After deployment, the item in the source stage will overwrite the item in the target stage, regardless of where the change was made.
Semantic models with configured deployment rules that haven't been deployed, are also marked as different, since deployment rules aren't applied until the semantic models are deployed from the source stage to the target stage.
Please check review changes to paired items for your report and make sure your data source has been rolled back successfully.
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hey Rico
Thank you for the speedy response. But, look, should not be the version restored after revert its commit (change)? In other words, in my understanding, case we restore old version in the source stage, the report must be overwrite to original version, meaning, would be the same without difference, right?
Hi @Johonnatan ,
I suggest you to refer to this blog to learn more details: Compare content in different stages before deployment - Microsoft Fabric | Microsoft Learn.
Different – An item that exists both in the source and the target stage, where one of the versions was changed after the last deployment. After deployment, the item in the source stage will overwrite the item in the target stage, regardless of where the change was made.
Semantic models with configured deployment rules that haven't been deployed, are also marked as different, since deployment rules aren't applied until the semantic models are deployed from the source stage to the target stage.
Please check review changes to paired items for your report and make sure your data source has been rolled back successfully.
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
6 | |
1 | |
1 | |
1 | |
1 |