Forum Discussion

WrigleyMedia's avatar
WrigleyMedia
Frequent Visitor
1 year ago
Solved

Unexpected error occurred while creating your data destination. Please try again later.

We are running a PowerBI trial and have created a data flow to pull data from another data source into PowerBI. Dataflow publishing fails with the error below with a Lakehouse data destination. Pleas...
Dataflow
  • v-ssriganesh's avatar
    v-ssriganesh
    1 year ago

    Hi WrigleyMedia,
    Thanks for following up.

    Since you have already validated the data types and confirmed that the API connection is working correctly, let’s explore other possible causes for the "Unexpected Error" when publishing to the Lakehouse.

    • Navigate to Dataflow Gen2 → recent runs and check for any warnings or hidden error messages beyond the "Unexpected Error." If you see an error code or additional details, please share them here for further analysis.
    • Create a new test Lakehouse and attempt to publish the Dataflow there. If it works, the issue may be specific to your existing Lakehouse.
    • Check you have the necessary write permissions for the Lakehouse.
    • Try publishing a small subset of data to see if the issue is related to specific rows or data volume limits.


    I trust this information proves useful. If it does, kindly Accept it as a solution and give it a 'Kudos' to help others locate it easily.
    Thank you.

v-ssriganesh's avatar
v-ssriganesh
Community Support
1 year ago

Hi WrigleyMedia,
Thanks for posting your query in Microsoft fabric community forum.

I want to acknowledge GilbertQ response it's partially correct, as checking the data destination and data types is an important step. However, I want to provide additional clarity regarding text data support in Fabric Lakehouse.

Text fields are supported in Microsoft Fabric Lakehouse, which is based on Delta Tables. Along with text, it supports numbers, currency, date, and time fields. The confusion might come from how Dataflow Gen2 maps source data types to the Lakehouse, which can sometimes cause issues if not mapped correctly.

Consider the below Steps:

  • Open your Dataflow Gen2 in Power Query.
  • Ensure that each column is mapped to the correct type before publishing.
  • Go to the Dataflow settings → Destination (Lakehouse) and check if there are any warnings about unsupported data types.
  • If the issue persists, load the data into a staging table first and then apply transformations before moving it into your final Lakehouse table.
  • Try publishing with just a few rows to see if a specific field is causing the issue.

Here’s a helpful Microsoft Learn article on supported types:
https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-data-destinations-and-managed-settings#supported-data-source-types-per-destination


If this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.

Thank you.