Forum Discussion
Solved
Power Query Table.NestedJoin bug
Apologies if this has been commented on before; I searched but am afraid there are many ways to describe this behavior. When I run this query below, I get exactly what I expect; an effective "cro...
Fair enough, thats a bug. As I said earlier, it should have thrown an error. But it is still an edge case and I don't see how this " bricks" power query, because there is a very simple and efficient work-around to give you (after expanding) a cartesian product of Table 1 and Table2:
= Table.Addcolumn(Table1, "Full Table2", each Table2)
Hi colecrouter
Hope you are doing well!
Could you please confirm if your query have been resolved the solution provided by Ilya_K . If they have, kindly mark the helpful response and accept it as the solution. This will assist other community members in resolving similar issues more efficiently.
Thank you
No, they have not provided a course of action to try.
v-karpurapud are you able to try the basic example in the comment above?