This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
I am getting a refresh error when loading a Dataflow into a Microsoft Fabric Lakehouse.
Error message:
Error Code: Mashup Exception Expression Error
We cannot convert a value of type Table to type Text
ErrorCode: Lakehouse036
The transformations are done in Power Query, and the error happens during the table insertion step.
Has anyone experienced this before?
Which Power Query step usually causes this error, and how can I identify the column returning a Table instead of Text?
Any help would be appreciated.
Solved! Go to Solution.
Hi @martymwas ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
Yeah. i resloved
Hi @martymwas ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
Hi @martymwas ,
We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.
Thank you.
Hello @martymwas,
Lakehouse036: A column contains a Table but a step expects Text. Check Power Query for columns showing “Table” and expand or convert them before loading.
Hello @martymwas
This error typically means that one of the columns in your Power Query still contains a nested value (a Table or Record), but a later step is trying to treat it as Text. In Dataflows Gen2 loading into a Fabric Lakehouse, this often shows up during the insert step as Lakehouse036. The most common causes are unexpanded columns after a Merge (Join) or Group By (All Rows), or an auto-generated Changed Type step that attempts to coerce a nested column to text.
To identify the issue, step back to the transformation just before the failure and inspect column data types. Look for columns showing as Table or Record in the profile. In many cases, simply expanding the merged/grouped column before applying text operations or type changes resolves the problem. Be especially cautious with blanket Changed Type steps, as these frequently introduce the error.
As a diagnostic approach, you can also add a temporary step to flag rows or columns that contain tables or records, helping pinpoint the exact source. In general, the correct fix is to expand and normalise nested structures rather than attempting to convert them to text, unless you explicitly intend to serialise them (e.g. to JSON).
Check out the April 2026 Fabric update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
| User | Count |
|---|---|
| 14 | |
| 10 | |
| 6 | |
| 5 | |
| 5 |
| User | Count |
|---|---|
| 37 | |
| 21 | |
| 16 | |
| 12 | |
| 11 |