Hi @jb_wedding ,
There is no definitive answer to this question, as different organizations may have different preferences and policies for managing their Power BI reports. However, some possible advantages and disadvantages of each option are:
- Option 1: Keeping the latest version locally in a shared folder (or repository)
- Advantages: This option may be easier to integrate with existing source control systems, such as Git or Azure DevOps, that can track changes, compare versions, and resolve conflicts in the PBIX files. It may also allow more flexibility and autonomy for the developers to work on their own copies of the files without affecting the published reports in the service.
- Disadvantages: This option may require more coordination and communication among the developers to ensure that they are working on the latest version of the files and that they do not overwrite each other’s work. It may also introduce some risks of losing or corrupting the files if the shared folder is not backed up or secured properly.
- Option 2: Assuming the master version of a Power BI report is always the published version in the service
- Advantages: This option may simplify the workflow and reduce the confusion of having multiple versions of the same report. It may also leverage the built-in version history and restore features of Power BI service, which can help recover previous versions of the reports if needed. It may also ensure that the developers are always working on the most up-to-date data sources and connections that are configured in the service.
- Disadvantages: This option may limit the ability to use other source control tools or platforms that can offer more functionality and integration than Power BI service. It may also create some dependency on the availability and performance of the service, which may affect the development process if there are any issues or downtime.
Ultimately, the best practice for the location of the master version of Power BI reports may depend on various factors, such as the size and complexity of the project, the number and skill level of the developers, the frequency and scope of changes, and the organizational policies and standards. Therefore, it is important to evaluate these factors and choose the option that best suits your needs and preferences. You can also refer to some of the resources below for more information and guidance on Power BI version control:
Power BI Governance, Good Practices, Part 2: Version Control with OneDrive, Teams and SharePoint Onl...
Power BI Version Control - Ready to use solution and free download
Best Regards,
Community Support Team _ kalyj
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
