Forum Discussion
Data Source Error - Column does not exist
- 5 years ago
Hi Anonymous ,
I've not worked with Amazon RedShift sources before, but you should be able to select your Source and Navigation steps within Power Query and see the original data as it's first pulled in. From here, you just go down the step list one-by-one and, when a step throws an error, look at the M code for that step in the formula bar and remove/update any reference to your missing/changed field name.
If you are getting an error even on the source step, I can only guess that the field list is hard-coded somehow into your connection string. You may be able to see more details on this using Advanced Editor on your query then, as above, updating any references to the offending field.
Pete
Hi Anonymous ,
I've not worked with Amazon RedShift sources before, but you should be able to select your Source and Navigation steps within Power Query and see the original data as it's first pulled in. From here, you just go down the step list one-by-one and, when a step throws an error, look at the M code for that step in the formula bar and remove/update any reference to your missing/changed field name.
If you are getting an error even on the source step, I can only guess that the field list is hard-coded somehow into your connection string. You may be able to see more details on this using Advanced Editor on your query then, as above, updating any references to the offending field.
Pete