Forum Discussion
Copy activity uses Linked services in Dev but Connection setting in UAT
v-karpurapud
Thnk you so much for responding to my message, I really appreciate it and appologies for late response.
I Create a new injestion pipeline and solved the issue.
Thanks again.
apturlov Thanks for responding.
Dev, UAT, PROD are different Workspaces
I do have the same lakehouse name in three different workspaces. "BL_IEDP" This is the lakehouse present in all three workspaces.
Below given is the screenshot of current copy activity.
The dynamic variable Item().TargetSchema gets the value "bronze" and Item().TargetSchema gets corresponding table name.
The issue is i wanted to move data from sql to bronze schema in lakehouse, unfortunately this copy activity is creating new schemas for each tables.
Thank you for reaching out to the Microsoft Community Forum.
You’re correct, having identical lakehouse names in different workspaces is fine, each workspace has its own separate BL_IEDP lakehouse but the copy activity must target the correct lakehouse and pass the table identifier in the exact format the sink expects. What you described (copy creating new schemas for every table) strongly points to a problem in the Table expression you are passing to the Lakehouse sink.
Use one combined expression for the Table field so the sink gets schema.table, for example concat(item().TargetSchema, '.', item().TargetTableName) (or @concat(item().TargetSchema,'.',item().TargetTableName)). Ensure the sink is pointed at the Tables root and the correct lakehouse connection (parameterize the lakehouse for safe deployments), set the Table action/writeMode to create or upsert so Delta tables are created, then run a debug and inspect the evaluated Table string in the pipeline run to confirm the exact target. If namespaces still appear, check TargetSchema/TargetTableName for stray characters (spaces, slashes) and paste the evaluated Table string here.
If you have any more questions, please let us know and we’ll be happy to help.
Regards,
Microsoft Fabric Community Support Team
v-karpurapud
Thnk you so much for responding to my message, I really appreciate it and appologies for late response.
I Create a new injestion pipeline and solved the issue.
Thanks again.Hi JibinSebastian
Thank You for the Update. If you have any more questions, please let us know and we’ll be happy to help.Regards,
Microsoft Fabric Community Support Team
Fabric Community is always a platform which helps me to solve my fabric related challenges. Thanks. In future if I face any I will definetly shoot it here.