Forum Discussion
Cannot Publish Dataflow (sourcing data from Excel SharePoint)
Hi, I've tried several times to publish a dataflow, but I keep getting the following error. It sources from a SharePoint folder, and transforms a few tables from a few excel files. It's not ...
Hey!
Would you mind helping us by answering some questions to better understand your situation?
- Does this solution work in Dataflows Gen1 in Power BI?
- What's the file extension of the files that you're trying to combine?
- What happens if you simplify your transform query and your queries overall to the most simplistic form? does it publish and run or does it also give you an error?
- Are you able to share some repro steps on how to reach this error? I've tried running this on my end but can't seem to be getting any isues however
- Several issues whilst trying to solve with MS Dataflow Gen2 will fail if - Last step in query has a Binary column - Some custom functions will work, some will not. I had a fnGetParameter custom function that kept failing - If the query name itself is too long, it causes some other string to spill over 128 characters, that will cause another error - Any lists or numbers in the query chain (where the final step of the query is in this form), will cause the whole Dataflow to fail We went through the above, shortened the query names, and it did publish! But then, it failed to refresh (since one of the tables, it gives this one the 2nd to last table in the query chain: Error Code: Mashup Exception Data Source Error, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Failed to insert a table. Details: [DataSourceKind = "Lakehouse", DataSourcePath = "Lakehouse", Message = "A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)", ErrorCode = -2146232060, Number = 10054, Class = 20] (Request ID: *************************************). The entire query chain takes 3-4 minutes in Excel. I thought Gen2 would zip through this in no time, but apparently not. I still can't get it to refresh reliably at all (not even once yet)
You could take a look at the limitations that we have today in Dataflow Gen2:
Data Factory Dataflow Gen2 limitations - Microsoft Fabric | Microsoft Learn
For the issue that you're reporting, it commonly only appears if you're using a Gateway. Are you currently using a gateway for that dataflow? if yes, please let me know if the article below works for you:
- How can I tell if I'm using gateway? All I can see for the dataflow settings is this: https://pasteboard.co/OriB64BUsFRg.png Do I need a better license?
- Several issues whilst trying to solve with MS Dataflow Gen2 will fail if - Last step in query has a Binary column - Some custom functions will work, some will not. I had a fnGetParameter custom function that kept failing - If the query name itself is too long, it causes some other string to spill over 128 characters, that will cause another error - Any lists or numbers in the query chain (where the final step of the query) is in this form, will cause the whole Dataflow to fail We went through the above, shortened the query names, and it did publish! But then, it failed to refresh (since one of the tables, it gives this one the 2nd to last table in the query chain: Error Code: Mashup Exception Data Source Error, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Failed to insert a table. Details: [DataSourceKind = "Lakehouse", DataSourcePath = "Lakehouse", Message = "A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)", ErrorCode = -2146232060, Number = 10054, Class = 20] (Request ID: *************************************). The entire query chain takes 3-4 minutes in Excel. I thought Gen2 would zip through this in no time, but apparently not. I still can't get it to refresh reliably at all (not even once yet)
