Forum Discussion
Column name changes in the data source errors in DAX
If you move to the step before Changed Type (i.e. before it breaks) and insert a step to rename the column from the new name (Number of Beds) back to your old name (Beds) that should result in the later steps working and the references to that field should then be recognised too.
If you move to the step before Changed Type (i.e. before it breaks) and insert a step to rename the column from the new name (Number of Beds) back to your old name (Beds) that should result in the later steps working and the references to that field should then be recognised too.
cpearson wrote:If you move to the step before Changed Type (i.e. before it breaks) and insert a step to rename the column from the new name (Number of Beds) back to your old name (Beds) that should result in the later steps working and the references to that field should then be recognised too.
Would that mean that Im reverting everything to the old names though? I dont want to do that. I do want to use the new names
Yes, it would use the old names, I thought you were looking for a quick and easy way to fix your report when your source data had changed field names.
The question is where do you want to see the new names and how much time do you want to invest to change it?
If the fields in your data source have changed names then you can either configure it to change them back to the original, so that all the work you've done downstream can remain intact, or you can work through all the errors to change each step to the new names. Or alternatively you could fudge the data load by changing them back to the original names, and then change the names of the fields/metrics in the visual side (but this will add confusion/complexity).
Also, regarding "Yes, Column Not found. Its looking for Bath not Number of Baths"... the step I suggested would fix one field "Beds" you'd need to repeat that for all the newly named columns.
It still seems a bit of an odd workaraound to rename from new to old and then back to new but I have documented it and it works
parry2k wrote:DebbieE then change column name in PQ what it is looing for, not sure where is the issue
The isssue was in my initial post. It seems the fix is to rename everything back to the old column names before all the applied steps.
Then to rename to the new column names at the end of all the applied steps and DAX will then use the new column names
The issue was, simply fixing the step that stopped working to the new column names and applying, DAX would still be looking for the old column names
DebbieE exactly, DAX doesn't care as far as the name is the name you might have tons of transformation on the way but if you are returning correct column name (as per you original table) than DAX should work Anyhow seems like you are aleady on the right track.
Would appreciate Kudos 🙂 if my solution helped.
