DataFlow gen2 - Sharepoint as a destination returns Mashup Exception error

[nareshraavi086]

Hi Everyone,

I am using the recently available feature in Fabric Dataflow gen2 with Sharepoint(still in Preview) as Destination.
here trying to copy files from Fabric lakehouse to Sharepoint but ended up with MashupException error.

Here is the exact error:
csv_WriteToDataDestination: There was a problem refreshing the dataflow: 'Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: The value is not updatable. Details: Reason = Expression.Error;ErrorCode = 10554;Detail = #table({"ColumnName"}, {});Microsoft.Data.Mashup.Error.Context = User GatewayObjectId: xxxxxx'. Error code: Mashup Exception Expression Error.

Note: I have data in my file and the last step of my power query is showing the data.
I tried copying the same file to another Fabric LH using the same duplicated dataflow gen2 and here i am succeeded.

can any one help me with this.?

Thanks in advance for you support.

[v-pnaroju-msft]

Hi @nareshraavi086,

Thank you for sharing your insights and approach in resolving the issue.

We kindly request you to mark your response as the accepted solution, as this will help other community members find answers to similar challenges more efficiently.
Please continue leveraging the Fabric Community for any further assistance with your queries.

Thank you.

[nareshraavi086 · Accepted solution]

Hello Luitwieler,

Thanks for reaching to me.
I read some leads in the MS Forums, I have deleted and recreated my Lakehouse and connections.

After that, my Dataflow gen2 pipelines are completed successfully. 
I didnt find any issue further to this.

Thanks.

[LuitwielerMSFT]

Hey @nareshraavi086 ! 

I am the PM driving the data destinations experience for dataflows gen2. 

Can you share what kind of settings you have setup for your filename, the folder you selected and other settings for the CSV file? 

We have observed that this happens when you add "/" or "\" in the filename to define a folder. However, the UX should prevent you now to configure as such. 

Jeroen Luitwieler