Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi ,
I am new with MS Fabric, contiuously practicing and able to create a dataflowgen2 with data destination warehouse/lakehouse and have a PowerBI connect to it.
Now I have a dataflowgen2 that will create a new table based on the data it will get from datasource, but i am getting this error "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., InnerException: Unable to create a table on the Lakehouse SQL catalog due to metadata refresh failure,"
What could be the reason of getting the issue?
Solved! Go to Solution.
Hi guys,
Thanks for your message 😃
I am not sure why, but i think i know what to do on my case, the issue issue only appear on my end if i click the publish button as soon as i update the DataFLow Gen 2.
What i do now is after updating Dataflow Gen2,
- i don't click click the Publish button right away,
- I click other tables first,
- close the Dataflow Gen2 to see the workspace again
- find the updated Dataflow Gen2
- wait for few minutes(1-5) because MS Fabric is slow in everything, i dont know if this is because im using Free Trial
- after waiting for few minutes, near the name of my dataflow gen 2 iclick the "Refresh now" button, the one that looks like circle
it is crazy because it works on my end. it seems there is a glitch or delay issue with MS Fabric.
The only issue now is when the dataflowgen2 is triggered by Pipeline, sometimes 'failed' sometimes 'Succeeded'
To Add, the problem seems to get solved after disabling staging of power query. Just by disabling staging, our loading speed was down to average less than 5 minutes and rarely get the error.
Here is one good way to test if this is a defect in Fabric or in your own code after you have disabled staging:
- Filter errors out from your results.
I would expect all of the code will result with something to store to the Lakehouse, so probably it should valid it through.
Hi guys, I am doing the Tutorial: Microsoft Fabric for Power BI users - Power BI | Microsoft Learn but I have the same issue when I clic on publish it fails, I already tried next solutions;
1.
What i do now is after updating Dataflow Gen2,
- i don't click click the Publish button right away,
- I click other tables first,
- close the Dataflow Gen2 to see the workspace again
- find the updated Dataflow Gen2
- wait for few minutes(1-5) because MS Fabric is slow in everything, i dont know if this is because im using Free Trial
- after waiting for few minutes, near the name of my dataflow gen 2 iclick the "Refresh now" button, the one that looks like circle
2. To Add, the problem seems to get solved after disabling staging of power query. Just by disabling staging, our loading speed was down to average less than 5 minutes and rarely get the error.
But any of them works, could please someone help me ?
When I clic on pulish appear this error.
Hi @dsajda,
Good day,
Upon checking the screenshot you've shared, It appears to be not the same with the error mentioned in this page.
You got:
Expression: We cannot convert a value of type Table to type Function.
Details
Reason = Expression.Error
Value = #table ({} {})
Please review your power query and see which part was set trying to convert a value of type Table into type Function.
Hi there,
When I try to disable DataflowGen2's Staging, it removes the destination Warehouse!
How do you solve this issue?
in my case i was having the same error when using Warehouse as data destination.
as soon as i changed from Warehouse to Lakehouse , the issue was gone..
Seems like a totally random error as my tables had very minimal transformations with no concatenation between multiple columns. In fact it had no new columns created at all... Almost feels like this is a bug of some sort.
Hi guys,
Thanks for your message 😃
I am not sure why, but i think i know what to do on my case, the issue issue only appear on my end if i click the publish button as soon as i update the DataFLow Gen 2.
What i do now is after updating Dataflow Gen2,
- i don't click click the Publish button right away,
- I click other tables first,
- close the Dataflow Gen2 to see the workspace again
- find the updated Dataflow Gen2
- wait for few minutes(1-5) because MS Fabric is slow in everything, i dont know if this is because im using Free Trial
- after waiting for few minutes, near the name of my dataflow gen 2 iclick the "Refresh now" button, the one that looks like circle
it is crazy because it works on my end. it seems there is a glitch or delay issue with MS Fabric.
The only issue now is when the dataflowgen2 is triggered by Pipeline, sometimes 'failed' sometimes 'Succeeded'
To Add, the problem seems to get solved after disabling staging of power query. Just by disabling staging, our loading speed was down to average less than 5 minutes and rarely get the error.
Thank you that Help 😀
Hi @je777999 ,
Thanks for using Fabric Community.
There are a few possible reasons why you might be getting this error:
Please refer to these links for more help:
DataFlow Gen2
Similar Issue
On-Prem Gateway Errors
Hope this helps. Please let us know if you have any further queries.
Hi @v-nikhilan-msft,
Any advice on how to achieve number 1? How do you remove the constraint?
Thanks.
Have I solved your problem? Please click Accept as Solution so I don't keep coming back to this post, oh yeah, others may find it useful also ;). |
If you found this post helpful, please give Kudos. It gives me a sense of instant gratification and, if you give me Kudos enough times, magical unicorns will appear on your screen. If you find my signature vaguely amusing, please give Kudos. | Proud to be a Super User! |
Hi Nikhilan,
Thanks for your comment.
In #1, how does one "remove the non-nullable constraint from the column" that is causing the dataflow Gen 2 to fail?
For now, I will replace null with 'Unknown', but I would be very much interested in the alternative that saves time and resources.
Thanks!
Hi @je777999 ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Please let us know if you have any further queries.
I have the same error,
jornada: Código de error: 999999, Detalles del error: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: No se puede cargar el archivo o ensamblado 'ParquetSharp, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ni una de sus dependencias. El sistema no puede encontrar el archivo especificado. Details: GatewayObjectId: 29a32c17-fdc7-4294-9961-d270354f1e9b (Id. de solicitud: 48d87264-360e-4d04-b47f-aac70f3fdc86).
We use Lakehouse and ensure that the DataflowGen2's Staging is set to disable. By default Staging is enabled.
Current setup
DataflowGen2 - use as ETL
Lakehouse - our data destination
never encountered the issue again, after disabling staging 😃 hope works on your end as well 😃
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
Check out the November 2024 Fabric update to learn about new features.
User | Count |
---|---|
5 | |
5 | |
3 | |
3 | |
2 |