Forum Discussion

colecrouter's avatar
colecrouter
Frequent Visitor
1 year ago
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...
General Comment
Need Help
  • PwerQueryKees's avatar
    PwerQueryKees
    1 year ago

    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)

     

PwerQueryKees's avatar
PwerQueryKees
Icon for Super User rankSuper User
1 year ago

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)

 

  • v-karpurapud's avatar
    v-karpurapud
    Icon for Community Support rankCommunity Support
    1 year ago

    Hi colecrouter 

    We are following up once again regarding your query. If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

    Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

     

    Thank you for your understanding and participation.