allows multiple developers to work collaboratively on the same PBIX. Idea could be separate back-end (advanced editor) and fron-end (modelling and report design) or allows the possibility to merge m...
You can decouple your ETL (Power Query M) & Model (DAX) from the Report definition using Analysis Services Tabular. If you have an Azure AS instance, you can even deploy the ETL & Model portion of a .pbix directly to it. This may not be an option for smaller organizations, as Analysis Services is far from free, but to those who can... The good: IT can govern the semantic model and still provide a lot of reporting flexibility to end-users. The bad: Analysis Services models at the 1400 compat-level are still crammed into a single-file .bim file... not a good thing for your VCS. The ugly: The Analysis Services tooling in SSDT for Visual Studio feels a bit abandoned. They ported the Power BI "Get Data" experience into SSDT a while back, which is great, but Power Query Groups are broken/unimplemented, making managing the ETL for larger projects a nightmare.
