Forum Discussion
Invoking function causes "Expression.Error: We cannot convert a value of type Record to type Number"
So why do you want to rename your columns, is it:
1. Because you get the error of duplicate column names, or
2. You want to rename your columns for another reason, but as a result you get duplicate column names?
In any case if you want to rename your columns so there won't be any duplicates, then you need to find some other solution for any duplicates, typically that would be adding a seqeunce number, e.g. if you have multiple "INFO CARD LINK" columns, then the first can be "INFO CARD LINK", the second "INFO CARD LINK.1", the third "INFO CARD LINK.2" and so on.
That would require a complete different approach.
Note: in Power Query, column names are case-sensitive, but when loading the result, you'll get an error (I guess that is the error you mentioned in your previous post).
So why do you want to rename your columns, is it:
1. Because you get the error of duplicate column names, or
2. You want to rename your columns for another reason, but as a result you get duplicate column names?
In any case if you want to rename your columns so there won't be any duplicates, then you need to find some other solution for any duplicates, typically that would be adding a seqeunce number, e.g. if you have multiple "INFO CARD LINK" columns, then the first can be "INFO CARD LINK", the second "INFO CARD LINK.1", the third "INFO CARD LINK.2" and so on.
That would require a complete different approach.
Note: in Power Query, column names are case-sensitive, but when loading the result, you'll get an error (I guess that is the error you mentioned in your previous post).
ah, I get it now... silly error on my part. My objective was to just to imporve the readability of column names, but that renaming has created a duplicate that I didn't originaly see. I should have actually though about what the error message was telling me...
Your solution works perfectly and I greatly apprecaite your expert help!