Forum Discussion

tayloramy's avatar
tayloramy
Icon for Super User rankSuper User
1 year ago
Solved

Error in Dataflow Gen 2 loading from Excel file on SharePoint Online

Hi,    I am working on a process to take Microsoft Forms data and put it into a database. To do this, I am doing the following steps:    1: Power Automate flow that runs when a response is submit...
dataflow
  • Alven's avatar
    Alven
    11 months ago

    Hi tayloramy ,

    is your SPO instance direclty accessible by Dataflows (e.g. not on-premises)? If so, you don't need to use a gateway and you would simplify the setup of the dataflows and get better performance. If your issue persists, can you please share the RequestId through DM?

     

    Thanks,

    Alessandro

v-aatheeque's avatar
v-aatheeque
Icon for Community Support rankCommunity Support
1 year ago

Hi tayloramy 

Thanks for sharing the error details. From the logs, the refresh is failing because the dataflow is trying to replace the table contents, but a temporary file path (_mashup_temporary) already exists in the Lakehouse. This results in a 409 – Conflict error.

 

Here are a few things you can check:

  • Since your dataflow replaces table data, confirm the overwrite option is correctly configured.
  • Make sure no other refresh/pipeline is writing to the same entity at the same time.
  • Failed or interrupted runs may leave behind _mashup_temporary files. Deleting these can often resolve the issue.
  • If you’re using Power Automate or scheduling frequent refreshes, allow some buffer time before the next attempt.
  • As a quick isolation step, try refreshing with a new Excel file stored in SharePoint to check if the issue is tied to the current path.

Hope this helps !!

tayloramy's avatar
tayloramy
Icon for Super User rankSuper User
1 year ago

Hi v-aatheeque

 

  • Since your dataflow replaces table data, confirm the overwrite option is correctly configured.
    • Yes, this is configured properly
  • Make sure no other refresh/pipeline is writing to the same entity at the same time.
    • Nothing else is touching this lakehouse at all
  • Failed or interrupted runs may leave behind _mashup_temporary files. Deleting these can often resolve the issue.
    • I deleted these files from OneLake Explorer, and the issue still remains
  • If you’re using Power Automate or scheduling frequent refreshes, allow some buffer time before the next attempt.
    • I am not, this is a daily refresh and no more frequent than that.
  • As a quick isolation step, try refreshing with a new Excel file stored in SharePoint to check if the issue is tied to the current path.
    • I have tried this and am seeing similar errors. First the file was in a Teams SPO site, and now it's in a native SPO site. Same issue.