Showing results for 
Search instead for 
Did you mean: 

Bug: Table.ReplaceValue kills all column types

When used in combination with "each" in the second argument, Table.ReplaceValue kills all existing column types (sets them back to any). Please fix:

Status: Accepted
Super User

Thanks @asarraf21 ,

great stuff!

Not applicable

The same problem happens whenever I create a new column with each as second argument.

This is particularly problematic in Direct Query scenarios where the operation of transforming the column back to the original data type is not supported. The solution, so far, doesn't help me at all.