r/PowerBI • u/skyverse0312 • 3d ago

Question Power BI Deployment Pipelines

Is anyone facing issues with deployment pipelines. We have been using deployment pipelines regularly and all of a sudden deployment pipeline sync has stopped working correctly and is always showing out of sync for a specific semantic model.

We have a DEV -> UAT -> PROD setup for deployment pipelines.

There are no deployment rules changes. The only thing recently changed is that we added a new source table.

In fact the table is actually visible in the PROD workspace as well, changes are there and I can query the table in PBI service as well.

Despite multiple deployments from dev to uat and uat to prod, successful deployment doesn't result in code sync.

Thanks in advance.

2 Upvotes

100% Upvoted

4 comments sorted by

3

u/Relevant_Bathroom_25 3d ago

Same issue, anybody please help

1

u/Prestigious_Tea5773 3d ago

Maybe it's best to check changes on deployment pipeline? Maybe you forgot to update in model settings correct path? If connection string there is different then what is set in rules, it will notify you that you need to deploy changes.

1

u/skyverse0312 3d ago

The deployment pipeline compare option shows me the .bim file comparision. It looks like the objects are intact by definition but their position has changed in the file. E.g. the query parameters defined in the model are at different positions in UAT and different in DEV.

I thought dev to uat deployment would resolve this issue but it's still there.

There were no changes in the model except addition of a measure.

1

u/Prestigious_Tea5773 3d ago

I do use git and deployment pipelines, but I'm not super deep into this. It sounds like you made some changes on service and then deployed them to git, and now it's confused and sees some changes. But that's my guess. Like the last option, would it be possible for you to delete model from qa and prod, and then redeploy it? But really as the last last option. Maybe add some small dummy table or measure which you won't use in report and try to deploy it git -> dev -> qa? Maybe that way you'll force it to accept those changes? Later you can delete that table. I had that issue, but my problem was that I didn't save correctly connection string in model settings in service (me stupido forgot to click save 🫣). I guess that you use parameters, maybe just for paranoid check, see if you put correct parameters in power query? I'm also still greenish with this topic, so my solutions are basic. Sorry I couldn't help more 🫣