Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
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.
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 4 | |
| 4 | |
| 4 |