Forum Discussion
Managing BI Updates with Multiple Editors For Contingency
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)
Please explain your scenario a bit more. What is the reason for replacing the PBIX rather than refreshing it?
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.
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)
