We have reports which are standard and deployed to 100s of customers. Each customer has their own workspace and database (schemas are the same). We use embedded reports in our application so we control the workspaces etc. Customers just see their reports.
Currently we have custom tooling written using the Power BI and Fabric Rest APIs. The existing release process involves
- Import the pbix to workspace
- Update the model connection string to point to client database associated with the workspace
- Bind the model to the correct connection object for authentication (Workspace Identity)
- Trigger a data refresh
For existing reports already on the workspace and not dependent on a model, we use UpdateReportContentInGroupAsync to update the report and maintain the ReportId.
So my question is what consideration are needed for migration to Git integration. I understand import will no longer be a thing, we will need to release by cloning standard reports over to the tenant release folder in the repo and then sync the workspace. But once done, how can connection strings be updated, can we still associate with a connection object for authentication?
I am struggling to find the right documentation for this. Deployment pipelines do not fit our model as we release from one standard report to hundreds of customers. It doesnt make sense to have Development/Staging/Production workspaces for each.
