PBIX published to service sometimes revert to old versions

[BerryBIA]

We have been running a large, complex Power BI model and reports for several years.  Occasionally, we update table connection strings to point to a dev table.  Like using Advanced editor to edit a table, saving changes, updating model, and publishing back to service, and Testing change.

This workflow is ok, but weve seen over time, sometimes after days or weeks go by with no issues, but the string we edited reverts back to its original text (unexplained).  Does this happen to anyone else ?

[Akash_Varuna · Accepted solution]

Hi @BerryBIA Yes, this issue can occur due to report overwrites from older PBIX files being republished, either manually or via deployment pipelines. It might also happen if multiple team members work on different report versions. To avoid this, implement strict version control, maintain a central PBIX repository, and ensure only the latest version is used for publishing.

[v-kpoloju-msft · Accepted solution]

Hi @BerryBIA,

Thank you for reaching out to the Microsoft fabric community forum.  Also, thanks to @Akash_Varuna, for his valuable insights on this thread. Here I mentioned few workarounds that might be resolve the issue. Please have a look into it.

From what you are described, it sounds like the connection string changes you have made (like switching to a dev table) work at first but later revert to the previous setup. While this might seem random, it’s usually caused by an older version of the PBIX being re-published either manually or through an automated process or a lack of version control across environments.

Use Parameters Instead of Hardcoding in M Code: Rather than editing connection strings directly in the query editor, try using Power Query Parameters. This makes it easy to switch between Dev, Test, and Prod environments without touching the query every time.  Dynamic M query parameters in Power BI Desktop - Power BI | Microsoft Learn

Set Up Deployment Pipelines (Pro/Premium): If you're using Power BI Pro or Premium, Deployment Pipelines are a great way to manage content across environments. You can define rules to automatically change parameters (like connection strings) as content moves from Dev to Test to Prod. Get started using deployment pipelines, the Fabric Application lifecycle management (ALM) tool - Mic...

Review Workspace Activity Logs: To check if an old version was re-published (possibly by someone else), you can review the Power BI activity logs or audit logs through Microsoft 365.  Track user activities in Power BI - Power BI | Microsoft Learn

Check Dataset Refresh History: Go to the dataset settings in the Power BI Service and review the refresh history. It may help you pinpoint when things reverted and if it aligns with a specific refresh or publishing event. Configure scheduled refresh - Power BI | Microsoft Learn

Use Version Control for PBIX Files: To keep track of what’s been published, consider storing your PBIX files in SharePoint, OneDrive, or even a Git repo. It helps maintain clear versioning and avoids accidental overwrites.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.

[v-kpoloju-msft]

Hi @BerryBIA,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-kpoloju-msft]

Hi @BerryBIA,

Hope you had a chance to try out the solution shared earlier. Let us know if anything needs further clarification or if there's an update from your side always here to help.

Thank you.

[v-kpoloju-msft]

Hi @BerryBIA,

Just wanted to follow up one last time. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.

[Akash_Varuna · Accepted solution]

Hi @BerryBIA Yes, this issue can occur due to report overwrites from older PBIX files being republished, either manually or via deployment pipelines. It might also happen if multiple team members work on different report versions. To avoid this, implement strict version control, maintain a central PBIX repository, and ensure only the latest version is used for publishing.