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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
markive
Advocate II
Advocate II

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

I am getting the following error:

 

 

Formula.Firewall: Query 'Query1' (step 'Added Custom') references other queries or steps, so it may not directly access a data source. Please rebuild this data combination.

 

In my first query I am accessing an API to get a list of URLs. In the second query it uses this list of URLs to then go back to the API and request all of the data.

 

I understand what the complaint is, but how do I get around it? I am actually always hitting the same domain for both queries, but maybe it doesn't know that. I suppose it wouldn't know that until runtime.

 

I have read that in Excel PowerQuery you can go to:

 

File=>Options and Settings=>Options and set the Ignore Privacy Levels option.

 

But no such option seems to exist in Powe BI Desktop. Does anyone know what I'm doing wrong or how I can get around this restriction, it seems like a common usage scenario?

 

 

 

1 ACCEPTED SOLUTION

 

Ken Puls blogged about this here

http://www.excelguru.ca/blog/2015/03/11/power-query-errors-please-rebuild-this-data-combination/



* Matt is an 8 times Microsoft MVP (Power BI) and author of the Power BI Book Supercharge Power BI.

View solution in original post

54 REPLIES 54

Hey mate, have you found any 2023 solution?

I always know it's a good solution when I see Matt's name!

Thank you Matt. That solved the problem. 

The error can occur from privacy permissions as well. It may be necessary to take the steps outlined in the solution above and also to change the privacy options.  File>Options and settings>Query Options>Privacy

Then choose "Always ignore privacy level settings".

Thanks, this solved my today problem!

I actually ran across this same error...

Going to: Options --> CURRENT FILE --> Privacy then setting the Privacy Level to "ignore the privacy levels and potentailly improve performance" did the trick.

 

Thank you so much guys!

@zuludogm 

Fernando

Anonymous
Not applicable

That was brilliant, it worked like charm!!! thank you 🙂

I'm getting same error but Im not using excel sheet but sql stored procedure query. Is there any solution for this?

I found this video which fixed my problem with excel sheets too. Check it out!

 

https://www.youtube.com/watch?v=z_kgvkgU8iI

@MattAllington Thank you for sharing, the Blog by Ken Puls, saved alot of my hair. (Very frustrating, but the below made sence and helped alot).

SNAGHTML409dfd44

Hi @MattAllington, thanks for the info.. 

 

Yes I was able to get around it just now by effectively moving all of the steps from the other query into the same query. This gets around the problem but it's a bit annoying.

 

@markive 

All steps in the same Query! Without "Reference"!!!

This did the trick!

You are a lifesaver!!!

Thank you so much!

Michael

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

Power BI Carousel June 2024

Power BI Monthly Update - June 2024

Check out the June 2024 Power BI update to learn about new features.

PBI_Carousel_NL_June

Fabric Community Update - June 2024

Get the latest Fabric updates from Build 2024, key Skills Challenge voucher deadlines, top blogs, forum posts, and product ideas.

Top Solution Authors