Forum Discussion
Formula.Firewall Error which disappears after reloading the data model in PBI Desktop
(Every merging step is executed in a seperate query)Per my current understanding (and I may be wrong) that is the issue. To avoid the formula firewall you should keep everything in the same partition.
Hi @lbendlin,
thanks for your answer. In my understanding a partition is created after a merging step is executed. That is why I changed my query from the single query (left) to the three queries (right).
How could I keep it all in the same partition if a new partiton is created after the merge? Or am I getting the term partitions wrong?
Important note: Privacy Levels are all set to organisational. Shouldn't the firewall not be a problem then?
Regards
KS
Avoid merging at all cost. Either do the joins further upstream, or use separate dataflows, or let the data model do the work for you.
Hi lbendlin
I'm trying this out at will let you know if it works. Unfortunately I have not been working with dataflows yet. All merging steps are executed in the end of my query. I will let you know how things turned out.
But thanks so far, I really appreciate it!
Regards
KSHi lbendlin ,
are there other transformations that I should avoid too? Like Invoking custom functions? It seems as if the error also appears for queries that do not have any merging steps at all. Therefore I use the expand function in the PQ UI that generates and invokes a automatically generated function.
Regards
KSAvoid anything that makes the Power Query engine think it is dealing with separate data sources. If you browse the interwebs you will find all kinds of trickery to create a smoke curtain so that the engine gets confused, and assumes everything is ok.
Small example: declare functions inside your query, not outside.