Continuous Deployment- Publishing Power BI Reports that leverage PowerBI Datasets to DEV/QA/PROD Embedded Resources

The topic is about an issue we are facing in “Continuous Deployment” process we built leveraging the Power BI REST APIs and Powershell scripts. Its working well in QA, but the challenge would be to deploying into the Production Power BI Embedded resource workspace.

Here is the problem description:
Let’s say,

Step 1. We have a power bi workspace “Build Workspace” in our Development/QA Power BI Embedded resource and have the Dev version of the PowerBI Dataset Model published in one of the Dev workspace using serviceaccount-dev@mycompany.com. Let's call this PowerBI Dataset as ‘Landing dataset’.

Step 2. The Report developers created all the required canned reports (around 15-20) connecting to the ‘Landing dataset’ and check-in into the GIT repository along with the PowerBI Dataset Model.

Step 3. Now, using deployment pipelines, when we publish these canned reports along with the PowerBI Dataset Model into any QA workspaces (in the same Devlopment/QA Power BI Embedded resource), the canned reports get published without any issues because the ‘Landing dataset’ exist and is accessible.

Step 4. Once published, using the same deployment pipeline, we Rebind (using REST API) the canned reports to their respective PowerBI Dataset Model within that workspace.

Step 5. Scene change: Moving to production!

Step 6. Pipeline Deployment process would login to production Production Power BI Embedded resource group using “serviceaccount-prod@mycompany.com” to deploy the Canned Reports and the PowerBI Dataset Model

Step 7. Now, when the Pipeline tries to publish the release versions of the canned reports to the production workspaces, it fails with a Bad Request error ("errorCode":"PowerBIModelNotFoundException") since the ‘Landing dataset’ does not exists in this Prod Power BI Embedded resource.

Therefore in the Continuous Integration/Continuous Deployment scenario, While publishing a report using the Power BI REST APIs, we should get an option/parameter in the Import method to specify the required PowerBI Dataset that it should be Rebinded and ignore what's in the .pbix file.