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
We found the answer provided by PwerQueryKees to be correct. Please consider trying it out to check if it works for you.
If they work, please consider marking them 'Accept as Solution', if not please share the details.
Thank You!