Forum Discussion
Formula.Firewall: Query references other queries or steps, so it may not directly access a data sour
Hi
I got the error in topic when trying to merge two tables in Power Query.
I've read a lot about solutions here in the community, but there's something that is bothering me.
The thing is that my model includes multiple tables from the same source and it seems like only one of them pops this error when trying to be merged.
What can be the cause for such "uniqueness"?
Thanks
Alex
Well, whatever the problem was resulting in this error only for particular one or two tables, I managed to resolve it using Excel Guru's guide (Ken Puls): http://www.excelguru.ca/blog/2015/03/11/power-query-errors-please-rebuild-this-data-combination/
Basically, as freder1ck brilliantly summarized: "...each query needs to be loaded into a staging query first. Then, you can combine these staging queries."
Just made two references from origianl queries then merged them. It seemed like it still put "i" sign, yet made the merge without me interfering in the privacy/security settings.
Thanks Fred! freder1ck
4 Replies
- tyw214
Helper I
i have the exact sme problem... did you ever get this solved? this actually just happened today as well.. the query was fine for months... and this problem just pop up now.
- Sasha
Helper III
Well, whatever the problem was resulting in this error only for particular one or two tables, I managed to resolve it using Excel Guru's guide (Ken Puls): http://www.excelguru.ca/blog/2015/03/11/power-query-errors-please-rebuild-this-data-combination/
Basically, as freder1ck brilliantly summarized: "...each query needs to be loaded into a staging query first. Then, you can combine these staging queries."
Just made two references from origianl queries then merged them. It seemed like it still put "i" sign, yet made the merge without me interfering in the privacy/security settings.
Thanks Fred! freder1ck
- v-chuncz-msft
Community Support
- Sasha
Helper III
No, got it today as well.
I'm trully clueless what might be the cause.
The common reason is a mix between external and internal sources resulting in security issues.
However, as I mentioned, all my tables come from the same excel, so it's beyond me why only one table is with the problem.
Alex