Bulk Update of Semantic Model Data Source for Multiple Reports

[VanThuan]

Hello everyone,

I have published a semantic model in my workspace, and I have multiple reports only for visual purposes that are solely based on that model. I now have a new version of the semantic model and would like to switch all reports to this new model at once. However, I want to ensure that I do not replace the old model, as that would delete all my historical data.

How can I accomplish this?

Thank you!

[andrewsommer · Accepted solution]

There is no native UI-based "bulk rebind" in Power BI, but there are two primary methods to achieve this but one involves the API and is not that straight forward.  The easiest approach is tedious but bullet proof

1. Open the .pbix file in Power BI Desktop (assuming you have a local copy or download from the Service).
2. Go to:
   1. Model View > Transform data > Data source settings
3. Click Change source > Select the new semantic model.
4. Ensure compatibility with fields, measures, tables.
5. Save and re-publish the report to the Service.

Watch out for broken visuals if there are schema compatibility issues between your two models. 

Particularly if you

1. Renamed or removed tables/fields/measures
2. Changed relationships or calculated columns

Please mark this post as solution if it helps you. Appreciate Kudos.

[rohit1991 · Accepted solution]

Hi @VanThuan ,

Currently Power BI does not provide a built-in feature for bulk updating or rebinding multiple reports to a new semantic model via the UI. As you noted, replacing the original model would erase historical data, so that's not an option. The most reliable method, although manual, is to open each report (.pbix) in Power BI Desktop, go toModel View > Transform Data > Data source settings, and update the data source to point to your new semantic model.

After ensuring schema compatibility (i.e., no renamed or missing tables, fields, or measures), save and republish each report. Alternatively, for a more scalable solution, you can consider using the Power BI REST API to programmatically rebind reports to a new dataset, but that approach requires scripting and administrative access. Always double-check for schema differences between the old and new models to avoid broken visuals. Hopefully, future updates to Power BI will include a more streamlined bulk rebinding option.

Passionate about leveraging data analytics to drive strategic decision-making and foster business growth.

Connect with me on LinkedIn: Rohit Kumar.

[v-echaithra]

Hi @VanThuan ,

May I ask if you have gotten this issue resolved?

If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Regards,
Chaithra.

[v-echaithra]

Hi @VanThuan ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

Regards,
Chaithra.

[v-echaithra]

Hi @VanThuan ,

We would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Regards,
Chaithra E.

[andrewsommer · Accepted solution]

There is no native UI-based "bulk rebind" in Power BI, but there are two primary methods to achieve this but one involves the API and is not that straight forward.  The easiest approach is tedious but bullet proof

1. Open the .pbix file in Power BI Desktop (assuming you have a local copy or download from the Service).
2. Go to:
   1. Model View > Transform data > Data source settings
3. Click Change source > Select the new semantic model.
4. Ensure compatibility with fields, measures, tables.
5. Save and re-publish the report to the Service.

Watch out for broken visuals if there are schema compatibility issues between your two models. 

Particularly if you

1. Renamed or removed tables/fields/measures
2. Changed relationships or calculated columns

Please mark this post as solution if it helps you. Appreciate Kudos.