Forum Discussion

Charley194's avatar
Charley194
Frequent Visitor
2 years ago

Issue with Dataflow Gen2 moving data to Azure SQL

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 o...
Data Integration
Fundamentals
Charley194's avatar
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's avatar
Charley194
Frequent Visitor
2 years ago

Can anyone assist with this issue?

  • v-cboorla-msft's avatar
    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

     

    • v-cboorla-msft's avatar
      v-cboorla-msft
      Microsoft Employee
      2 years ago

      Hi Charley194 

       

      We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

      In case if you have any resolution please do share that same with the community as it can be helpful to others.
      Otherwise, will respond back with the more details and we will try to help .

       

      Thanks

      • Charley194's avatar
        Charley194
        Frequent Visitor
        2 years ago

        hi, no resolution.  It is now consitently coming up everytime I have a date column, regardless of tables or datasource involve.  The only work around is that I have to re create the Gen2 flow every time I need to get data into the Azure SQL.   I have spoken to a 3rd party and they know what the issue is and can hopefully help.  Should know more by the end of the week