This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
I've been digging in to the M language, and one of the principles I've learned is that a statement using Table.NestedJoin should usually be followed by a statement using "Table.ExpandTableColumn". I was told this can improve performance, but I am not clear on why that is. If anyone could give me some additional information on this, it would be greatly appreciated.
Thanks.
Solved! Go to Solution.
Merely expanding the tables after the nested join preserves query folding. It's still not as fast as plain old Table.Join.
--Nate
Merely expanding the tables after the nested join preserves query folding. It's still not as fast as plain old Table.Join.
--Nate
Very helpful answer. 😄
Okay, that helps. Thanks.
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.