Forum Discussion

McSarah's avatar
McSarah
Helper I
5 years ago
Solved

Unpivot + unknown columns + data type woes

Hi, I am trying to refactor an existing set of queries to take advantage of query folding, and I've run into trouble with an unpivot step. This step worked in the original (which used custom SQL to j...
Need Help
  • Anonymous's avatar
    Anonymous
    5 years ago

    Hi McSarah 

     

    So you are here in this step, and my giant list of columns is your column name list? You don't wrap it with {} as it is already a list, you can directly reference it or #"my giant list of columns" if it does have space...also seems missing closing ) and ,

     

    #"Expanded second half of join" = Table.ExpandTableColumn(Source, "other query - second half of join", { ( my giant list of columns)}

      

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Hi McSarah 

 

I don't see anything wrong with this step, do you have any error? Or actually you have trouble with your next step, how did you do the Unpivot?

McSarah's avatar
McSarah
Helper I
5 years ago

Yes, the problem is with the subsequent step - the step I shared above appears to work, but the subsequent unpivot still thinks it's a problem that the original column is a double. I thought maybe "number" wasn't specific enough in the conversion?

I eventually "solved" this problem by converting the double to a currency type (the unpivot appears to accept currency + int). However, this step breaks query folding and is not dynamic in case of future datatype conflicts. So it works for now but is not ideal.