Forum Discussion
Power BI developer mode (.pbip) merge conflict issues
Anonymous That's true, but you left something out. I've been working with version control in Power BI since it was introduced and released last summer. And it has one problem that should have been solved before the release, but hasn't been solved yet. If any changes were made to the pbip. file, no matter what, Power BI will randomly swap different code blocks that have nothing to do with the changes made. And this is actually a big pain in the ass, because it basically not only breaks the whole concept of version control but also leads to unjustified conflicts any time you are trying to merge changes.
Let me know if you find a solution to this problem. Right now its really stopping me from fully using versioning, because I need to do a manual copy-over merge every now and then.
I'm still not aware of any solutions to this problem. Every release becomes hell and comes down to numerous merges/cherry picks flavored with manual edits.
That sounds awful.
During my research on this issue, I found this "project" to improve exactly the sorting issues we are experiencing.
I haven't checked in detail, but maybe this is relevant and might even be a viable workaround:
https://richardswinbank.net/ssas/ssas_tabular_merge_conflicts
Do let me know if this could worksausaged Thanks a lot for sharing this! In essence model.bim turned out to be a json file, so we can actually play around with its content just as with report.json. I took the idea you shared as a basis and wrote my own simple Python code that sorts the contents of all nested structures, just because it's easier for us to maintain it in Python rather than with shell. We've been testing this approach for a couple of weeks now and I must say that now if conflicts do arise, they are intuitive and resolved in the code editor, so thank you again.