Forum Discussion
Formula firewall error - possible bug
See Ken Puls's blog Power Query Errors: Please Rebuild This Data Combination for a workaround that sets up the external query as a function. Why you have to trick PBI like this I'm not sure...
Yes, I've seen that post. The question is, why is the formula firewall activating in the first place in our scenario? It sure seems like a bug to me.
I think's it's supposed to be a feature rather than a bug, designed to prevent inadvertant security breaches - per https://social.msdn.microsoft.com/Forums/en-US/69153a6d-2205-4456-bcac-3a4689c787cf/parameterising-queries?forum=dataexplorer
"we have tried to optimize for the non-advanced user to do things easily and also protect them from cases like the above. For the more advanced user scenarios, they may need to go a bit off the happy path to make the scenario work, such as enabling this non-default mode."
I agree the product could be more helpful than just presenting "Formula firewall error"... Add as an Idea?
Sorry, this just does not make sense to me. What security risks are there if the data sources are all local and are marked as such in their respective privacy settings? Everything is in the same folder on the same local disk.
There must be a specific condition that triggers the firewall in this instance. I've reviewed that MSDN forum thread linked to the last reply and Miguel's response does not cover the scenario we encounter. Again, I am familiar with both the intention of the formula firewall and the privacy controls - it's just that these intentions does not appear to be applied properly in our instance.
