Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live 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.
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
| User | Count |
|---|---|
| 16 | |
| 9 | |
| 8 | |
| 7 | |
| 7 |