Forum Discussion
PowerBI Pipeline detected differences although no recent changes is made
Hi PowerBI community, I found a weird bug when using PowerBI pipeline
The scenario is, we are using git integration on release branch for our INT workspace, which our all the reports in our INT workspace is deployed to our PROD workspace. Once deployed, we will merge our release branch to master branch, and repeat the cycle again next deployment by creating a new release branch from the master branch and will deploy again once the new release branch connected to INT workspace.
The weird thing is, Report A and Semantic model A havent been changed at all during the cycle but PowerBI pipeline is detecting a differences in report(which is not viewable in the change history inside PowerBI pipeline).
and recently, we have deployed our Report A and Semantic Model A on wednesday, made no changes, but suddenly on thursday, it detected there is differences between Report A in PROD to be compare with INT, and we dont even change the branch yet.
Anyway can help to resolve this problem? We cant simply redeploy the report to PROD without confirming the changes
Hi Kei88 Yes, refresh history can affect sync if only PROD was refreshed and not INT. For removing cache you will have to republish it , revalidate the pipeline, redeploy from INT to PROD, and check workspace bindings for conflicts.If issue still persists contact MS Support
4 Replies
Hi Kei88 The issue might be metadata changes or sync discrepancies. Try checking the metadata (refresh history, permissions, workspace bindings) or clearing the Power BI pipeline cache. If the issue persists, contact Microsoft Support.
Oh so refresh history also will affect the sync between two workspace? since i have refreshed only on PROD for semantic model but not in INT, and how do i clear the powerBI pipeline cache?
Hi Kei88 Yes, refresh history can affect sync if only PROD was refreshed and not INT. For removing cache you will have to republish it , revalidate the pipeline, redeploy from INT to PROD, and check workspace bindings for conflicts.If issue still persists contact MS Support
