Hello Jani,
the requirement and issue we face is the following:
1) We add PBIX files in the Asset library which are using direct query connection to the localhost server and the DW DB of D365. These files are developed in D365 cloud-hosted development box environments
2) These files serve as Power BI datasets where all DAX measures are implemented e.g., YTD Sales, YTD Quantity, etc. All RLS rules are defined in the Power BI dataset as well, e.g., RLS rules showing only, domestic sales, or international sales, or all sales etc
3) We deploy this PBIX files (Power BI datasets) via the respective environments (TEST, PROD, UAT) in LCS to the powerbi.com platform using a services account
4) We share the deployed dataset of the service account in powerbi.com to our users having a Power BI Pro license in the organization
5) Then users create Power BI reports consuming the Power BI dataset deployed via our service account and they consume these reports via the powerbi.com portal and the Power BI mobile App
6) We also publish Power BI reports using the deployed Power BI datasets to Power BI Apps
The issue starts if we need to add/modify either a DAX measure or a RLS rule. Without versioning we cannot redeploy the new Power BI dataset to be used from the existing reports. Instead we have to add a new PBIX file in the Asset library, deploy it via LCS to the respective environment as a new Power BI dataset and edit all existing reports to use the new dataset. Roll-back is also following the same process.
Thus, it would make sense to have versioning of Power BI assets. Did I help you to better understand the requirement and the issue we try to address?
