Forum Discussion

EdMk's avatar
EdMk
New Member
9 months ago
Solved

Dataflow Gen2 Mashup Error

The first Dataflow Gen2 to Lakehouse destionation is running ok. But from the second I`m getting this error: WriteToDataDestination: There was a problem refreshing the dataflow: "Couldn't refresh...
  • shashiPaul1570_'s avatar
    9 months ago

    Hi EdMk,

    This error is coming from the gateway, not the Lakehouse or Dynamic schema itself.
    The pattern “Error in committing version … We can’t update the value … Detail = #table({"Version","Published","Data","Modified"}, {}) … Error code: 999999” is a known issue with older on-premises data gateway versions when a Dataflow Gen2 writes to a Lakehouse and does a Replace on later refreshes.

     

     

    Ask your admin to update the on-premises data gateway to the latest version (Manage gateways → select the gateway → if “Update” appears, run it, or download the latest build and install it).

     

    1. After the gateway upgrade, re-publish the dataflow and run the refresh again.

    2. If it still fails, try temporarily switching the destination mapping from Dynamic schema to a fixed schema just to confirm it’s only the gateway issue; then log a Fabric support ticket with the refreshed Request ID.

    Also you can follow this  link for your reference. 

    https://community.fabric.microsoft.com/t5/Dataflow/Dataflow-Gen-2-Error-in-committing-version/m-p/3992121#M3133

     

    If this helps, please give it a kudos 👍 and mark it as Accepted Solution so others hitting the same Dataflow Gen2 Mashup error can find it easily.

     

    Thanks & Regards

    Shashi Paul