The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
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
Solved! Go to Solution.
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
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
We haven’t heard back from you on the response provided by @rohit1991 and just wanted to check if your query has been resolved. If not, please share more details so we can assist you further.
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.