Forum Discussion
Dataflows: Link Entities Error in refresh
Hi all,
I have a Dataflow with Calendar Tables and it is working and refreshing normally everyday. When I created a new Dataflow where I linked a table from my Calendar's Dataflow, both not refreshing and I am receiving an error
| Error: Expression.Error: We cannot convert the value "1" to type Number.. RootActivityId = .Param1 = Expression.Error: We cannot convert the value "1" to type Number. Request ID: |
Which when I delete the linked tables without changing anything to the source table the refresh is back to normal.
Both Dataflows are under the same Workspace and on Premium Capacity.
Any Ideas or workarounds?
Thank you in advance
Eleftheria
hi elia22gr ,
Your issue is likely a data type mismatch in the linked Dataflow. Try these fixes:
- Ensure Data Type Consistency – Set column types explicitly in both Dataflows.
- Manually Convert Columns – Use Table.TransformColumnTypes() for numbers or dates.
- Check for Non-Numeric Values – Add a custom column to detect errors:Table.AddColumn(Source, "Check", each try Number.FromText([Column]) otherwise "Error")
- Recreate the Linked Entity – Deleting and re-linking may resolve metadata issues.
- Ensure Data Type Consistency – Set column types explicitly in both Dataflows.
I deleted all the steps and rewrite the same code and worked. I was saving and refreshing it at each step.
7 Replies
Hi elia22gr - you can check the datatypes in dataflow like example, if any column expected to be a Number has Text values.you can set the original Calendar Dataflow to refresh first before the new Dataflow.Adjust refresh schedules to ensure the Calendar Dataflow completes before the dependent Dataflow starts. remove the link and relink the tables if necessary.
I hope the above options should helps.
hi elia22gr ,
Your issue is likely a data type mismatch in the linked Dataflow. Try these fixes:
- Ensure Data Type Consistency – Set column types explicitly in both Dataflows.
- Manually Convert Columns – Use Table.TransformColumnTypes() for numbers or dates.
- Check for Non-Numeric Values – Add a custom column to detect errors:Table.AddColumn(Source, "Check", each try Number.FromText([Column]) otherwise "Error")
- Recreate the Linked Entity – Deleting and re-linking may resolve metadata issues.
- Ensure Data Type Consistency – Set column types explicitly in both Dataflows.
Hi all,
It is insain that it cannot convert 1 to number. 1 is a number! This error comes from a column that has 1 and 0. So, I changed it to true and false as a text and still gives me the same exact same error.
I deleted all the steps and rewrite the same code and worked. I was saving and refreshing it at each step.
Hi elia22gr
Thank you for reaching out microsoft fabric community forum.It seems that your issue have been resolved . If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi elia22gr
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi elia22gr
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
