Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
markive
Advocate II
Advocate II

Formula.Firewall Query Foo references other queries, so it may not directly access a data source.

I am creating a lot of reports but they always hit the same API's on my app. To try to speed up the manual creation of reports I created a table called APISettings with a ProjectURL column. This means I only need to change a single field to reconnect all my queries to another URL.

 

This works great, but now I cannot merge two tables in PowerQuery as it gives me the error:

 

Formula.Firewall Query Foo references other queries, so it may not directly access a data source.

Doing some research in PowerPivot you could just set this setting to be ignored, but I cannot see how to do this in PowerBI?

 

Is there another way of registering my DataSource so that multiple queries all KNOW they are accessing the same one and can therefore allow merge etc?

 

 

1 ACCEPTED SOLUTION
pqian
Microsoft Employee
Microsoft Employee

Hi @markive, the Firewall error is thrown when one evaluation is trying to access more than one data sources. Normally we partition your query automatically to split it into multiple evaluations across data sources, but there are some cases where this partitioning isn't smart enough. Can you post the query which has this problem?

 

Alternatively, you can turn this off in Options->Global->Security->Privacy Levels->Always Ignore (machine wide), or Options->File->Privacy (for the current file)

View solution in original post

4 REPLIES 4
pqian
Microsoft Employee
Microsoft Employee

Hi @markive, the Firewall error is thrown when one evaluation is trying to access more than one data sources. Normally we partition your query automatically to split it into multiple evaluations across data sources, but there are some cases where this partitioning isn't smart enough. Can you post the query which has this problem?

 

Alternatively, you can turn this off in Options->Global->Security->Privacy Levels->Always Ignore (machine wide), or Options->File->Privacy (for the current file)

How can I do this in Visual Studio for AAS?

@pqian thanks! I didn't know about that settings.. 

 

I can't find the Machine Wide setting, but the Current File one has done the trick!

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.