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

Compete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.

Reply
rnb
Regular Visitor

Error: The column " " of the table wasn't found

I am having this error come up whenever I try to do data tranformations in select columns of a table that I'm working with. However, I have no idea what could be causing this - there's no " Changed Type" step, the only step before these transformations is the source. I have not changed any column names or moved things around. My source is SurveyMonkey, and I did edit one of the questions in order to prevent having duplicate columns titles - could that be causing this? The column titles do match the questions as they are now, though. I don't what other issue this could be. If the edit is causing this, is there a way around it? 

 

Thanks!

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @rnb ,
According to your description, this is usually caused by not being able to get a column with a matching name. In Power Query, if you get a duplicate column in the data source, Power Query automatically adds a different suffix to it to distinguish it, and the first duplicate column still retains its original name. To resolve this issue, you can try to see if there is an action at the data source that changes the properties of the column. Secondly, you can also delete this step to see if the other code works correctly. You can back up the original code before deleting it.

Best regards,
Albert He

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

View solution in original post

1 REPLY 1
Anonymous
Not applicable

Hi @rnb ,
According to your description, this is usually caused by not being able to get a column with a matching name. In Power Query, if you get a duplicate column in the data source, Power Query automatically adds a different suffix to it to distinguish it, and the first duplicate column still retains its original name. To resolve this issue, you can try to see if there is an action at the data source that changes the properties of the column. Secondly, you can also delete this step to see if the other code works correctly. You can back up the original code before deleting it.

Best regards,
Albert He

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

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

Top Solution Authors