Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
Johonnatan
Helper I
Helper I

Revert Azure DevOps commit/push but difference remains in Power BI pipeline

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

Johonnatan_0-1722522310626.png

 

Sync status OK

Johonnatan_0-1722522440399.png

 

Pipeline status

Johonnatan_1-1722522184661.png

 

Does someone know what's wrong?

1 ACCEPTED SOLUTION
v-rzhou-msft
Community Support
Community Support

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.

 

View solution in original post

3 REPLIES 3
Johonnatan
Helper I
Helper I

@v-rzhou-msft 

 

Maybe, this flow will clarify more.

 

Johonnatan_0-1722608716313.png

 

Johonnatan
Helper I
Helper I

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?

v-rzhou-msft
Community Support
Community Support

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.

 

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

AugPowerBI_Carousel

Power BI Monthly Update - August 2024

Check out the August 2024 Power BI update to learn about new features.

August Carousel

Fabric Community Update - August 2024

Find out what's new and trending in the Fabric Community.

Top Kudoed Authors