Forum Discussion
PowerQuery removes nullable binary field when saving data flow, making full folder load impossible
- 5 years ago
MarlonK
I have experienced the same issue and expanded the Binary column in the Dataflow itself then connected from Desktop.________________________
If my answer was helpful, please click Accept it as the solution to help other members find it useful
Click on the Thumbs-Up icon if you like this reply š
MarlonK
I have experienced the same issue and expanded the Binary column in the Dataflow itself then connected from Desktop.
________________________
If my answer was helpful, please click Accept it as the solution to help other members find it useful
Click on the Thumbs-Up icon if you like this reply š
- MarlonK5 years agoHelper I
Yeah, that seems to be the only choice.
- Icey5 years agoCommunity Support
Hi MarlonK ,
This is casued by this warning:
Based on my test, after you choose "save & close", it automatically deletes these columns with complex types.
Best regards
Icey
If this post helps, then consider Accepting it as the solution to help other members find it faster.
- Data-estDog2 years agoResolver II
Can you elaborate on this solution? I am not familiar with what you mean by "Expand the binary colum in the dataflow".
My thought was to use a view on the source system and conver the binary to varchar.- Jake7702 years agoNew Member
Might be kind-of late, but I had the same problem and derived the answer from Fowmy response. What he means is to click on the [Binary] column of the row (csv file) that you want so the [Binary] field is not returned by the dataflow. If you have a query to gets the list of files and then other queries that reference that list, you can instruct the dataflow to not load the query that gets the list. You do this by right clicking on the query that contains the [Binary] content and unselect the Enable Load option. Bottom line is the dataflow will not allow you to return a binary data type out of your dataflow.