cancel
Showing results for 
Search instead for 
Did you mean: 
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 III
Super User III

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 III
Super User III

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

Helpful resources

Announcements
PBI User Groups

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group!

MBAS on Demand

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

July 2021 Update 768x460.png

Check it out!

Click here to read more about the July 2021 Updates

Power Query PA Forum 768x460.png

Check it out!

Did you know that you can visit the Power Query Forum in Power BI and now Power Apps

Top Solution Authors
Top Kudoed Authors