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

Grow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.

Reply
npnigro
Advocate III
Advocate III

Formula.Firewall error appearing when it shouldn't?

I've been dealing with the "Formula.Firewall" issue for a long time. Since I didn't need to use the scheduled refresh feature of the Power BI service, I would disable the privacy checking. But now I need to use the scheduled refresh feature for some of my most complex data models. I've gone through and added "staging" queries to address a number of the Formula.Firewall errors, but now I'm running into a weird situation. 

 

In a nutshell, I can resolve the Formula.Firewall errors I'm seeing without actually changing any of the queries. First, I click "Refresh" in Power BI Desktop to update all tables, and I'll quickly get the Formula.Firewall error for a table.  I then go into the queries editor and visit the table that's giving me the problem. I see the error and then start to visit the tables that are being merged into this query. For many of these dependent tables, I see the "Unexpected error: Evaluation was canceled" message and I click retry. If I do that for all the dependencies, I eventually get back to the main table that was giving me the error and the error magically goes away!

 

If I go back to the main Power BI Desktop screen, I need to click Refresh again because none of the queries have actually changed -- I've just refreshed them in the query editor. I will then see the Formula.Firewall error for another table and I'll have to repeat the process I described above. This takes a really long time and I have to do it every time that I refresh the data model.

 

I can't explain why I'm getting these errors or why my workaround resolves them. I'd greatly appreciate help from someone on what's going on here and how I can fix it once and for all. 

2 REPLIES 2
v-ljerr-msft
Employee
Employee

Hi @npnigro,

 

Ken Puls post a good blog on this issue, and a workaround is also mentioned there. Could go to check if it helps in your scenario. Smiley Happy

 

Regards

Thanks! I'm very familiar with this blog and the concept of using "staging" queries to avoid the error. This approach is necessary to avoid the error generally. In my case, I'm able to clear the error just be interacting with the previews of queries in the query editor. See my description above. 

Helpful resources

Announcements
RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.

MayPowerBICarousel

Power BI Monthly Update - May 2024

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