I am trying to move data from a Gen1 dataflow into an Azure DB using a Gen2 flow. I have got this to work and have moved the data. I did come against this error and I found dealing with this in a own flow was the answer. Now when I am trying to refresh the data I am coming up with this error. Note I am trying to replace all data in the table. Nothing has change in the SQL DB the data is going to, and nothing in the flow has changed. Can anyone assist with this issue? I have checked that there are no errors in the column mentioned.Just to update, I can get this to work if I recreate the flow. But when I refresh the flow I get this error. Note I am not using the flow to create the table.

Hi Charley194 Apologies for the delay in response. I have repro the same scenario from our end and didn't find any issue if the schema is matching. Please find the screenshots attached. Result: I tried to mismatch the schema and then got the same error. Error result: Try to recheck once the schema and try to refresh the dataflow. If the issue still persists please check the gateway version and upgrade it to the latest version. Please refer to Link for more details on the latest gateway version. I hope this helps. If you have any further questions please do let us know. Thanks

Hi Charley194 Thanks for using Fabric Community. Apologies for the issue you have been facing. Could you please explain what is the source data here? What do you mean by Dataflow Gen1 here? These details would help me to understand the issue better. Thanks

Many thanks. The source is a Dataflow. So I have loaded the data into a dataflow and I load that into the Gen2 dataflow to get it into the Azure DB. Does that make sense? I have discovered that I can't load the data directly in the Gen2 Dataflow.

Hi Charley194 Thanks for the details. Can you please provide some repro steps about how you are loading the data? Some screen shots would also help.

Sure, this is the dataflow, with the M code. As you can see, it is some sort of issue with the column type on InvoiceDate, but the type Date is the same in the Dataflow and in the Azure SQL so I am a little confused and it did work the first time I use the flow. The result Destination table in Azure DB

Issue with Dataflow Gen2 moving data to Azure SQL

12 Replies

v-cboorla-msft
Microsoft Employee
2 years ago
Hi Charley194

Thanks for using Fabric Community.

Apologies for the issue you have been facing.

Could you please explain what is the source data here? What do you mean by Dataflow Gen1 here? These details would help me to understand the issue better.

Thanks
- Charley194
  Frequent Visitor
  2 years ago
  Many thanks. The source is a Dataflow. So I have loaded the data into a dataflow and I load that into the Gen2 dataflow to get it into the Azure DB. Does that make sense?
  I have discovered that I can't load the data directly in the Gen2 Dataflow.
  - v-cboorla-msft
    Microsoft Employee
    2 years ago
    Hi Charley194
    
    Thanks for the details. Can you please provide some repro steps about how you are loading the data? Some screen shots would also help.
Charley194
Frequent Visitor
2 years ago
Sure, this is the dataflow, with the M code. As you can see, it is some sort of issue with the column type on InvoiceDate, but the type Date is the same in the Dataflow and in the Azure SQL so I am a little confused and it did work the first time I use the flow.

The result
Destination table in Azure DB
- Charley194
  Frequent Visitor
  2 years ago
  Can anyone assist with this issue?
  - v-cboorla-msft
    Microsoft Employee
    2 years ago
    Hi Charley194
    
    Apologies for the delay in response.
    
    I have repro the same scenario from our end and didn't find any issue if the schema is matching. Please find the screenshots attached.
    
    Result:
    
    I tried to mismatch the schema and then got the same error.
    
    Error result:
    
    Try to recheck once the schema and try to refresh the dataflow.
    
    If the issue still persists please check the gateway version and upgrade it to the latest version. Please refer to Link for more details on the latest gateway version.
    
    I hope this helps. If you have any further questions please do let us know.
    
    Thanks
kakaur
New Member
2 years ago
Hi, This might be an issue with Data Gateway version. Try contacting MS Support. We had a similar issue and had to downgrade the Data Gateway version on our end to get it resolved.