Forum Discussion
Best practices for multiple developers working on the same Power BI report, publishing with gateway
- 11 months ago
Hi rookieda
1) Can you publish without breaking gateway/refresh:
Yes, Publish to the same workspace and choose Replace the existing dataset (same name). The gateway mapping and refresh schedule stay. If prompted, click Take over and re-enter credentials. Only reconfigure the gateway if you added/renamed data sources.2) Best practice for two developers (with gateway):
-
Give both devs Contributor in the workspace and add both as Users on the gateway data sources.
-
Split model and report: publish the semantic model once; build reports as thin reports (live connection). Report changes don’t touch refresh/gateway.
-
Prefer a service principal (or shared admin account) as dataset owner for scheduled refresh.
-
Use Deployment Pipelines (Dev >> Test >> Prod): assign workspaces, set rules to swap parameters/gateway per stage, then Promote forward.
-
Keep files in SharePoint/OneDrive or Git (PBIP) for versioning; agree on “one person edits at a time”.
-
When schema or data sources change, update gateway data sources/mappings first, then publish.
-
Hi. In my opinion, the best approach is using Power BI projects PBIP with repos. Considering you are just asking about PBIX, I have written what I think is best in the following article: https://blog.ladataweb.com.ar/post/716223048431386624/git-versionando-powerbi-trabajando-en-equipo
You can translate it to english. It shows how to work with repo + pbix + one person editing at one time locking file.
The article also shows an architecture to automate an auto publish to service scheduled or manually.
I hope that helps,