Managing BI Updates with Multiple Editors For Contingency

[BreakConcrete]

How to Get Data and Visual Updates to Be Reflected in BI Dashboard Published to SharePoint when you have multiple editors for contingency plan. 

Currently, myself and the other editors replace an existing PBIX file for updates in SharePoint, but lately the updates are no longer reflected. Now I have to remove everything from the workspace, replace them with file with the new updates, republish the dashboard to SharePoint Page, and reset scheduled refresh via the Semantic model to see visual and data updates. There's always things changing and this has become a time consuming process.

We also need multiple editors so updates can happen if I'm on PTO. Is there a way to make data and visuals update automatically without resetting everything each time there's an update?

[v-prasare]

Hi @BreakConcrete ,

if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support

[v-prasare]

Hi @BreakConcrete ,

if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

@lbendlin, thanks for your prompt response

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support

[lbendlin]

Please explain your scenario a bit more.  What is the reason for replacing the PBIX rather than refreshing it?

[BreakConcrete]

The file has to get replaced when myself or the other editors make updates to the data or visuals based on management requests. In the past, just replacing the existing file reflected all updates when refreshed. Now the updates aren't reflected when replacing the existing file and refreshing.

[lbendlin · Accepted solution]

You can choose different levels of developer cooperation

- Storing the PBIX on a sharepoint and communication among developers so you don't overwrite each other's work (but you have versioning as a safety net)

- Using deployment pipelines to propagate changes

- using Version control integration via Github Enterprise or Azure DevOps

- a combination of the above (for example DEV and PRO deployment pipeline with DEV linked to Github)