Power BI On prime servers - upgrade to September 2025

[RPBI1]

Hello, Recently we have upgraded CCT PBI servers to 2025 September version , all existing report working fine. But ran into issues:

1. when promoting report with small changes from Dev to SIT , new changes are not showing up in the SIt environment .

2. Same report when I promote from Dev to UAT environment , report in UAT showing incorrect datasource information its not matching with Dev datasource.  Does anyone ran into this issue before.  Since we have upgrade all environments this has became urgent issue to resolve. Appriciate your help.

thanks

[v-pgoloju]

Hi @RPBI1,

Great to hear that it’s working as expected on your end!
I’d suggest marking the specific reply that helped resolve the issue as the accepted solution, as this can benefit others facing similar problems. It will make it easier for community members to quickly identify and apply the right fix.

Thnaks & Regards,

Prasanna Kumar

[v-pgoloju]

Hi @RPBI1,

Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.

Best regards,
Prasanna Kumar

[RPBI1 · Accepted solution]

It started working after downloading report to upgraded power bi desktop and refreshed datasoruces and exported back to the server then migrated report to SIT environment. 

[v-pgoloju]

Hi @RPBI1,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @123abc  for prompt and helpful response.

When moving a report from Dev to SIT, Power BI sometimes keeps using the old dataset instead of fully replacing it, so new changes don’t show up unless the dataset is redeployed or removed and deployed again. When promoting to UAT, the dataset can also end up connecting to the wrong datasource or gateway without any clear warning, especially if gateways have similar names or use OAuth/user-based connections. A practical fix is to always deploy the dataset (semantic model) along with the report, re save or reapply the deployment rules, and then manually check and rebind the datasource and gateway in the target workspace.

Thanks & Regards,

Prasanna Kumar

[123abc]

Community sovled problem link may help you:

Solved: Power BI Report Server September 2025 has been Rel... - Microsoft Fabric Community

[RPBI1]

Hi @123abc  : I don't see the solution to my problem with the report promotion. Can you past direct link.

thanks