Forum Discussion
Resolver IFailed to save modifications to the server. A deleted QueryGroup is referenced by a Partition or Exp
I have a model which has been set up with connections to a Sharepoint domain. I'm now trying to change the SharePoint connections to another domain. I've changed the connection strings and credentials in Power Query but, the refresh halts with the above error (screenshot below).
I can copy individual queries to a blank model and can get them to return the data from the other domain... so, its not a credentials or connection issue.
Other posts have suggested turning off the "meta data" option but, this is no longer possible in the latest update of Power BI.
Any suggestion would be appreciated.
I think I stumbled onto the solution. Pressing "Refresh All" on the Preview in Power Query appears to resolve the problem.
6 Replies
SteveD2I think I stumbled onto the solution. Pressing "Refresh All" on the Preview in Power Query appears to resolve the problem.
doostAdvocate I
"Refresh all" did not help in my case. The issue was that the names of the query groups (just the groups you make in Query Editor) were changed. Resetting these to the original names fixed the issue. That leaves me with the old - less clear - query group names, but at least there is no error anymore... Very weird that changing the group name is not covered by PowerBI...
shubh25Helper I
This resolved my issue as well. Not very helpful as I have changed sources and old group names are indicative of the sourcenames that were being used earlier. But it resolved the issue for now. Thanks for this.
Hi, I know that I am ages later, but I just stumbled on the same problem: I had been reordering querries and doing some slight renames of tables, nothing too fancy. Then the same error raised its ugly head.
In my case the reason was fascinating twist on "changed names" issue: renaming GROUP of tables from "data quality" to "Data quality". Yes only one lower case -> upper case letter change. Bang.
Reverting name to old version did fix the issue (unlike the "Refresh all" solution.) 🙂