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

The Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.

Reply
manutremo
Frequent Visitor

Stack overflow error when deleting structured column without expanding it first

I'm merging two tables using Left anti join as part of the processing of a dataflow. The purpose of this merge is just deleting some rows in the main table based on the content of the other table. This works perfect, and as a result I get a structured column as expected. However with Left anti the resulting structured column just contains nulls, so I just delete it as the following step. This works fine in the power query interface, but fails with a memory error or a stack overflow error during refresh.

 

It, however, works fine if I first expand the table and then delete the resulting column. So there seems to be an issue with deleting a structured column without expanding it first, which would look like a possible bug.

 

Has someone experienced the same?

1 ACCEPTED SOLUTION
edhans
Super User
Super User

There are several oddities with deleting a column created from a nested join. It also breaks folding.

Rather than an anti-join, consider using a simple filter that uses List.Contains() - or in your case - not List.Contains(). This article will walk you through the equivalent of an inner join without creating unnecessary columns. By putting "not" in front of List.Contains, it will become an anti-join.

Using List.Contains To Filter Dimension Tables — ehansalytics



Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

DAX is for Analysis. Power Query is for Data Modeling


Proud to be a Super User!

MCSA: BI Reporting

View solution in original post

1 REPLY 1
edhans
Super User
Super User

There are several oddities with deleting a column created from a nested join. It also breaks folding.

Rather than an anti-join, consider using a simple filter that uses List.Contains() - or in your case - not List.Contains(). This article will walk you through the equivalent of an inner join without creating unnecessary columns. By putting "not" in front of List.Contains, it will become an anti-join.

Using List.Contains To Filter Dimension Tables — ehansalytics



Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

DAX is for Analysis. Power Query is for Data Modeling


Proud to be a Super User!

MCSA: BI Reporting

Helpful resources

Announcements
Feb2025 Sticker Challenge

Join our Community Sticker Challenge 2025

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

Jan NL Carousel

Fabric Community Update - January 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors
Top Kudoed Authors