This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
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 May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 7 | |
| 7 | |
| 6 | |
| 5 | |
| 4 |