Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Data Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more

Reply
Anonymous
Not applicable

Table.NestedJoin with Table.ExpandTableColumn

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.

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Merely expanding the tables after the nested join preserves query folding. It's still not as fast as plain old Table.Join.

 

--Nate

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

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. 😄

Anonymous
Not applicable

Okay, that helps. Thanks.

Helpful resources

Announcements
Fabric Data Days is here Carousel

Fabric Data Days 2026

Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.

May Power BI Update Carousel

Power BI Monthly Update - May 2026

Check out the May 2026 Power BI update to learn about new features.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.