Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredJoin us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM. Register now.
Gen2 pipeline fails with source Excel files from Sharepoint folder, load into Lakehouse table.
"Mashup Exception Data Source Error, foutdetails: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Failed to insert a table."
I read a lot about the 'mashup' errors in this community, but all seem to involve an OnPrem or external source. But in this case it's all MS-cloud, as my ETL goes from a Sharepoint folder through a Gen2 PowerQuery into a Lakehouse table.
On the workspace status page, I do see both the SharepointList as the Lakehouse have a valid connection status through OAuth2 on privacylevel organizational. Seems it has to do with 'Failed to insert a table.'
As advised tried to create a support-ticket to MS through the admin-portal, but while filing it says 'failed to send the request, go to startpage and try again' while all requestform-fields are completed succesfully.
As such, I'm posting my issue on this forum.
Solved! Go to Solution.
UPDATE: sorry members for claiming your precious time to read my post. Just tried a bunch of workarounds to get the issue fixed. First was to remove all excisting connections from within the PowerQuery editor. As I read the error message 'Failed to insert a table' so thought it canot create a table in Lakehouse.
But the error log was deceptive as it didn't have to do with the Lakehouse but just with the query itself. Added a 'replace all errors with null' for all columns in the query. Seemed some rows needed column type 'any' but that ain't supported yet, and text didn't solve it. Now I've had a succesfull load.
@Member123456 Post can be closed.
UPDATE: sorry members for claiming your precious time to read my post. Just tried a bunch of workarounds to get the issue fixed. First was to remove all excisting connections from within the PowerQuery editor. As I read the error message 'Failed to insert a table' so thought it canot create a table in Lakehouse.
But the error log was deceptive as it didn't have to do with the Lakehouse but just with the query itself. Added a 'replace all errors with null' for all columns in the query. Seemed some rows needed column type 'any' but that ain't supported yet, and text didn't solve it. Now I've had a succesfull load.
@Member123456 Post can be closed.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Fabric update to learn about new features.