Forum Discussion
Deployment pipeline not detecting report changes
Today we found out that deployment pipeline doesn't work properly.
Business user informed us he made changes on the report, but when checking deployment pipeline, it doesn't show changes at all.
We tested it with multiple deployment pipelines, multiple workspaces, in most cases it didn't detect changes.
When we added new report, it was detected.
So, just checking if anyone else has this issue?
I was using deployment pipeline last week and it was working fine.
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.
13 Replies
Hello nandic,
Deployment pipelines detect PBIX file updates or new reports. Changes made directly in the service (browser editing) may not trigger detection.
To ensure the pipeline picks up updates, republish the report from Power BI Desktop. New reports are always detected, which matches what you observed.GilbertQ and Olufemi7 , thank you for your responses.
Until now, deployment pipeline recognized when the report was edited in Power BI service.
This is how we have been working on one project: business analysts can do some minor changes on dev workspace (change text, update default filters) and then we deploy changes to prod workspace using deployment pipeline.
Each time, when going to deployment pipeline, the report that was edited by business analysts was marked as different between dev and prod.
Note: i agree, deployment pipeline doesn't show what are actual changes on report between dev and prod, but it detected changes. And for changes on semantic model, it also shows actual changes.
But since yesterday, it doesn't work like this anymore..Hello nandic,
Thanks for clarifying, you’re correct.
Service-side report edits (text, filters, formatting) have historically been detected by deployment pipelines as metadata differences. If this suddenly stopped across multiple pipelines and workspaces, that’s not expected behavior and may indicate a backend/service issue rather than a design limitation.
I will recommend checking the Fabric/Power BI Service Health dashboard and, if the issue persists, opening a Microsoft support ticket with workspace IDs and timestamps so they can trace it.
If it was consistently working before and stopped “since yesterday,” that strongly suggests a service-side regression.
Hi nandic , Just following up to check if your issue has been resolved. If you are still facing any difficulties, please let us know and we will be happy to assist further.
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
V-yubandi-msft thank your for the response and making it clear.
I expected answers like:
1. Yes, deployment pipelines detect changes if users edited reports online
2. No, deployment pipelines do not detect changes if users edited reports online
However, i didn't expect answer:
3. Maybe it does, but maybe it doesn't 🙂
Thank you,
Nemanja
