Forum Discussion
DataFlow is not replacing table in Fabric OneLake
Hi Guys,
I have a table like this:
and this is coming from this query in dataflow:
what i have done , i added the new step to add new test column into this and run "Save & Run":
But new column eventhough the Update method is replaced...didnt work! Why?
new column is not appearing in OneLake environment...
Best,
Jacek
Hi jaryszek
When you add a new column in a Dataflow and run Save & Run, the change is applied inside the dataflow but it doesn’t always show up in OneLake unless the output settings are refreshed. The “Update method = Replace” only overwrites the table structure that was already mapped, but if the schema in OneLake isn’t refreshed, the new column won’t appear.
Here are a few things to check:
-
Confirm the destination mapping : In the Dataflow output settings, go to Column mapping and make sure the new column is mapped to the OneLake table. If it’s not mapped, OneLake won’t include it.
-
Run a full refresh : Sometimes incremental or cached runs don’t push schema changes. Try running a full refresh of the dataflow.
-
Verify OneLake table schema : Open the table in OneLake Explorer or SQL Endpoint and check if the column exists at the schema level. If it doesn’t, the mapping didn’t apply.
-
Consider schema drift settings : If your workspace has schema enforcement on, new columns may be blocked until you explicitly allow schema drift or remap the output.
-
3 Replies
Hi jaryszek
When you add a new column in a Dataflow and run Save & Run, the change is applied inside the dataflow but it doesn’t always show up in OneLake unless the output settings are refreshed. The “Update method = Replace” only overwrites the table structure that was already mapped, but if the schema in OneLake isn’t refreshed, the new column won’t appear.
Here are a few things to check:
-
Confirm the destination mapping : In the Dataflow output settings, go to Column mapping and make sure the new column is mapped to the OneLake table. If it’s not mapped, OneLake won’t include it.
-
Run a full refresh : Sometimes incremental or cached runs don’t push schema changes. Try running a full refresh of the dataflow.
-
Verify OneLake table schema : Open the table in OneLake Explorer or SQL Endpoint and check if the column exists at the schema level. If it doesn’t, the mapping didn’t apply.
-
Consider schema drift settings : If your workspace has schema enforcement on, new columns may be blocked until you explicitly allow schema drift or remap the output.
Hi jaryszek
Just checking in to see if you had a chance to review the previous response. If you still need assistance, please let us know and we’ll be glad to help.
-
