Forum Discussion

rookieda's avatar
rookieda
New Member
11 months ago
Solved

Best practices for multiple developers working on the same Power BI report, publishing with gateway

Hi Community, We are a team of two developers working on the same Power BI report. My teammate built the initial version and currently handles publishing to the Power BI Service. I’m now makin...
Need Help
  • rohit1991's avatar
    rohit1991
    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.

rohit1991's avatar
rohit1991
Super User
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.