Forum Discussion
undefined
- Anonymous1 year ago
Hi Sureshmannem ,
Thank you for the follow-up. We would be happy to assist you!
Upon my knowledge, this is a known limitation when using Copy Activity with Delta Lake tables in Fabric , the “Import Schema” feature is not supported, which explains the inconsistent behavior you are seeing with locked or missing column mappings. This is documented in the official guidance here: Copy data from/to Lakehouse – Limitations.
For more context, you may also refer to the link: Data Factory limitations in Fabric.
Hope this helps.
Thank you.
Hi Sureshmannem ,
I wanted to follow up to see if you had a chance to review the previous response provided by us. I hope it was helpful. If yes, please Accept the answer so that it will be helpful to others to find it quickly.
Thank you.
Hi Anonymous ,
Thank you for your support and prompt follow-up.
Unfortunately, the current workaround isn’t resolving the issue. The copy activity against Delta Lake/Warehouse is not effectively managing column mappings.
- At times, the schema is recognized but doesn’t allow changes to the mappings.
- In other instances, the schema is ignored entirely, leaving blank fields.
I’m exploring alternative approaches using notebooks to overcome these limitations.
Best regards,
Suresh