Forum Discussion

bjstigall's avatar
bjstigall
Frequent Visitor
7 years ago
Solved

Formula.Firewall: Query references other queries or steps, so it may not directly access a data ...

 I have 2 queries importing into PowerBI.  The come from two different SQL Servers.  Both SQL Servers have the privacy level set to Organizational.  When I merge the queries together, i get the dread...
  • v-jiascu-msft's avatar
    v-jiascu-msft
    7 years ago

    Hi bjstigall,

     

    It works well in my test. Can you share more details? Please check the privacy again as the snapshot shows.

    Formula-Firewall

     

    Best Regards,
    Dale

v-jiascu-msft's avatar
v-jiascu-msft
Microsoft Employee
7 years ago

Hi bjstigall,

 

It works well in my test. Can you share more details? Please check the privacy again as the snapshot shows.

Formula-Firewall

 

Best Regards,
Dale

KimStahl94's avatar
KimStahl94
Helper I
4 years ago

Hi v-jiascu-msft ,

may I please ask you a question.

I have the same issue but I do only query data from this one single SharePoint source. 

I do have several merging and expanding steps in my queries which is why tried this to get around the issue. So my orignial query changed to this. As you can see there are about 7 merging steps within DIM BWA which should result in the article's partitions. The path of the query is highlighted and the error occurs always within this path. I also implemented a staging area and I tried the idea in Ken's post by using custom functions. Ignoring privacy levels does not help either. My problem is also the irregularity of given error. It appears just occasionally and for different query steps in the DIM BWA path. So sometimes I do not get the error at all. I have no idea what I am missing. If you need further details let me know. 

 

Looking foreward to your reply

KS