Forum Discussion
Replace a data source for an Existing report where the new data source has different fields
I assume the problem you're seeing is that when you import, the Query Editor is giving alerts about those columns not existing?
The easiest way to fix this is to go into the Query Editor, replace your source table, and press the Advanced Editor button. This will bring up the entire list of code used to transform that table. Look near the top, and there's probably a line that starts with #"Changed Type". Go through that line, and remove the bracketed sections that include columns that you've removed.If you didn't use the columns in any of the rest of the transformations, you should be able to hit Done and go on your merry way. If the query editor still gives you similar "The column 'name' of the table wasn't found." style error messages, look through the rest of the code in that advanced editor, and continue removing references to the removed columns.
Once the code no longer references those columns, you should be all set!
Resident RockstarI assume the problem you're seeing is that when you import, the Query Editor is giving alerts about those columns not existing?
The easiest way to fix this is to go into the Query Editor, replace your source table, and press the Advanced Editor button. This will bring up the entire list of code used to transform that table. Look near the top, and there's probably a line that starts with #"Changed Type". Go through that line, and remove the bracketed sections that include columns that you've removed.
If you didn't use the columns in any of the rest of the transformations, you should be able to hit Done and go on your merry way. If the query editor still gives you similar "The column 'name' of the table wasn't found." style error messages, look through the rest of the code in that advanced editor, and continue removing references to the removed columns.
Once the code no longer references those columns, you should be all set!
Thanks, that has worked, the advanced editor code looked quite short because it doesn't word-wrap, but when I pasted in into a text editor and searched I was able to find the fields causing the errors and remove them.
Sorry for the slow reply, I've been working on the Excel side of my project and only got back to PowerBi today.
