Point Thin Report at New Premium Capacity

[AxiomaticOne]

We have one Premium Capacity and we just got another Premium Capacity.  We have hundreds of users who like and use Power Point live visuals and Bookmarks and Subscriptions.  We also use Deployment Pipelines (dev-uat-prd). Finally, thin reports are split from the datasets, thin reports in one workspace/deployment pipeline and datasets in another workspace/deployment pipeline. I've already redployed the dataset I want to move to a new set of dev-uat-prod workspaces/pipeline.

Question: I want to simply repoint my dev-uat-prd thin reports attached to my first workspace/capacity, to the new capacity that has the new copy of the dataset so that my end users don't have to re-do all their embeds, bookmarks, and subscriptions.

I don't think this is possible, what say you?

[blopez11]

If your reports in dev-uat-prd will point to the same workspace/semantic model, then I believe it can be done.

- Open the pbix file in the desktop.

- Select Transform data, then Data source settings

- Select the current semantic model from the list, then Change Source

- Select the new model from the list, then select Create

- You may see a dialog to select the tables to connect to.  Review/update, then select Submit

- Close the Data source settings dialog

- Validate your report

- Save and publish to your dev workspace.

- Validate your report in dev, then promote through the pipleline.

Hope this helps,

[AxiomaticOne]

@blopez11 that does not work actually because the new report that you publish is pointing at a different data set it thus has a different lineage. So when you go to publish that through, it doesn't overwrite the existing copy in UAT to PROD and you then have two reports name the exact same thing but the user artifacts are all pointed at the original, not the new

[AxiomaticOne · Accepted solution]

Resolution: https://learn.microsoft.com/en-us/rest/api/power-bi/reports/rebind-report-in-group

So, apparently I just needed to search for rebind instead of repoint.  Read the above Microsoft article. We did this using the "try it" feature of the REST API and it worked perfectly to resolve my original problem.