Forum Discussion

AndrewPF's avatar
AndrewPF
Helper V
5 months ago
Solved

merging direct query queries

I have a number of Direct Query queries in my Data Transform view.  It works fine until I try to put a merge in one of them.    I have found a workaround which is to simply duplicate the query, the...
Need Help
  • AndrewPF's avatar
    AndrewPF
    5 months ago

    Thank for your replies but I'm still getting issues even when I use the duplicates solution.  I have changed the DQ to import and the problem has gone.  As far as I can gather, my data will still refresh (I don't need it in real time). 

BeaBF's avatar
BeaBF
Super User
5 months ago

AndrewPF 

Yes, the error message is basically pointing to the right issue.

What’s happening is that when you add a merge in DirectQuery, Power Query can treat it as a “data combination” and the privacy/firewall logic kicks in. That’s why it complains about referencing other queries.

Your workaround (duplicate + merge) works, but it’s more of a patch than a clean solution.

Cleaner options would be:

  • If both tables come from the same source, do the join directly at the source (e.g. SQL view) → best for DirectQuery

  • Or make sure the merge can fully fold (same source, simple steps, no intermediate query dependencies)

  • Also check privacy levels, as mismatches can trigger this exact error

BBF


💡 Did I answer your question? Mark my post as a solution!

👍 Kudos are appreciated

🔥 Proud to be a Super User!