Issue with Copy Job and Variable Library: Destination Schema and Table Name becomes Invalid

Hi hhuikuri ,

Thank you for reaching out to the Microsoft Community Forum.

Copy Job does not support schema/table paths, only plain table names. Copy Job only supports dynamic table names when the connection is static. Once the connection itself is variable-driven:

1. schema cannot be overridden

2. table mapping becomes “best-effort”

3. metadata lookup fails

4. Copy Job reverts to default: dbo.<table>

This is why your result remains the same no matter what table name you type.

Note: Copy Job cannot dynamically change schema when using variables by design it is a current limitation.

Please try below alternative workarounds.

1. Keep connection static, only parameterize table name. If your Lakehouse does not change, do NOT store connection ID in Variable Library.

Instead, Use the normal Lakehouse connection, Only set destination table name = variable

Example:

Schema Table
dbo @{variables('tableName')}

2. Use Pipelines instead of Copy Job, If you must parameterize connection ID, workspace ID, lakehouse ID: Pipeline Copy Activity supports dynamic schema + table fully. Copy Job does NOT.

Please refer below link.

How to create a Copy job in Data Factory - Microsoft Fabric | Microsoft Learn

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh