Forum Discussion
Dataflow (gen2) error: Couldn't refresh the entity because of an issue with the mashup document
I had to rebuild the Lakehouse completely to resolve this issue. I used the same dataflow (gen 2) to achieve this outcome.
Microsoft EmployeeHi andyemiller
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.
Thanks
I had to rebuild the Lakehouse completely to resolve this issue. I used the same dataflow (gen 2) to achieve this outcome.
In my case, I had to rebuild the Lakehouse to ingest data from a dataflow. Since this time, I have experienced Mashup issues when the field types are not consistent with the source and destination data. Usually, a change is made to the source data (Salesforce in my case) that has not been replicated to the Lakehouse. I usually edit the Lakehouse field by rebuilding the table structure, using an SQL statement, and then use the dataflow to rebuild the connection between the source and destination. The work takes a "hot minute," but has not been a hurdle since this earlier issue.