Hi, we do regularly change or update the PQ data source via "Data source settings".
That is very convenient as you reach several queries by one stop. And normally it works.
So what could be the reason for provoking this message:
The query table couldn't be refreshed:
The query 'xyz' or one of its inputs was modified in Power Query after this connection was added. Please disable and re-enable loading to the Data Model for this query. *
[*Actually deloading and reloading is no solution in case of several interdepending queries or self-referencing queries.]
I had also a case where a "connection only" broke down. The connection to the pivot base (no PP) was destroyed.
The sources are beside of the name completely identical files, just with a different data status (or for test purpose even the same data!).
Today I tried in two "blocked" files to apply the source change instead of via "Data source settings" in the first step ("Source") of the queries itself and it worked. Well, I am happy that it worked, but isn't it strange that one source changing can block the refresh and another doesn't. Same for why did it work via "Data source settings" several times and then suddenly not.
Hi Matthias,
That error is caused when you load a table from Power Query to the Power Pivot Data model and subsequently make changes to that table in Power Pivot e.g. rename a column. By renaming that column in Power Pivot you break the relationship Power Query has with that column. It can't find it anymore because it has a different name.
This post explains the issue in detail: https://blog.crossjoin.co.uk/2014/09/08/power-pivot-power-query-read-only-connection-problems-in-excel-2013-and-what-to-do-about-them/
Mynda
Hi Mynda,
thanks, but this is about power query only - no power pivot involved and also no loading to the data model (completly empty).
Also in the case you describe the connection gets greyed out and here I did not see anything like this. On top only updates via "Data source settings" were blocked and changing the source directly in the query was fortunately(!) possible - means the connection itself was functional.
In the mentioned cases all queries grabbing external data are connection only and were not changed.
Hope you have a hint what might provoke this problem.
Regards,
Matthias
Hi Matthias,
Do you ever get this error when you edit the source M code via the Advanced Editor? That's the way I always change the source. Maybe it's something to do with the Data Source Settings route.
I've never seen this error. Are you able to share files so I can reproduce it?
Mynda
