Forum Discussion
Deployment pipeline not detecting report changes
Hi nandic ,
Thank you for clarifying. Deployment pipelines are able to reliably detect changes when a report or semantic model is republished from Power BI Desktop. However, if changes are made directly in Power BI Service such as editing titles, filters, or formatting these are considered service-side metadata changes and may not always trigger change detection in deployment pipelines.
This means you might see the change indicator appear inconsistently when making edits in the service.
To ensure consistent detection in the pipeline, it is best to republish the report from Power BI Desktop before deploying.
Thank You.
V-yubandi-msft
We need to clarify something:
If user makes changes on report in Power BI service (changes title or default filter), will deployment pipeline show indicator that this report has been changed?
Note: i do not expect to see what has been changed, this feature was never visible for reports. But at least it was showing indicator that the report has been changed.
Now it doesn't, or it does randomly.
Example:
A few days ago i changed one report and it showed change.
Yesterday i did change on exact report, but it doesn't show change in deployment pipeline.
In both cases, i made changes directly on Power BI service.
As Olufemi7 mentioned above "Changes made directly in the service (browser editing) may not trigger detection.". I am not interested in "it may happen" answer.
Either detection works or doesn't work?
Hi nandic ,
Thank you for clarifying. Deployment pipelines are able to reliably detect changes when a report or semantic model is republished from Power BI Desktop. However, if changes are made directly in Power BI Service such as editing titles, filters, or formatting these are considered service-side metadata changes and may not always trigger change detection in deployment pipelines.
This means you might see the change indicator appear inconsistently when making edits in the service.
To ensure consistent detection in the pipeline, it is best to republish the report from Power BI Desktop before deploying.
Thank You.
Hello V-yubandi-msft,
we are facing the same issue and we are following the way your are recommending.
We are publishing the report from Power BI Desktop to dev workspace and then we are deploying to production via deployment pipeline.
For us it was not detecting any change. The change we made was on page level filter. Is it posible that it simply doesn´t consider the filters while checking for changes?
At the end in production our filter changes are not displayed even if we have them in dev and are publishing to prod via pipeline.Best regards, Thomas
If you republish the report from Power BI Desktop to the Dev workspace, the deployment pipeline should normally pick up the change. Page level filter changes are included in the report, so they should be reflected after republishing.
If the pipeline isn’t detecting the change and the update isn’t showing in Production, it could be a temporary issue. You can try republishing the report to Dev and redeploying through the pipeline.
If it still doesn’t work, consider raising a support ticket for further investigation.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thank You.
Hi, I am facing the same issue as this thread, but cannot download the report to Power BI Desktop as the option is greyed out. The report does not exist in Power BI Desktop. How can I get my item deployed?
If the Download PBIX option is greyed out, it typically means the report was created in Power BI Service or is linked to a dataset that doesn’t allow downloads.
Deployment pipelines can still deploy the report if a change is detected, but since this thread is about detection issues, that could be causing the problem.
As a workaround, you might try making a small edit, such as changing a title or filter, to see if the pipeline recognizes it. If that doesn’t work, you may need to recreate or move the report to Power BI Desktop for more consistent deployments.
Thank You.
