Destination Table Name Missing in Copy Activity

[scca]

I recently noticed that my Copy activities that previously had destination table defined using dynamic content are now appearing empty. Oddly enough that hasn't caused any errors or failed my jobs as they are still running fine with the intended output. This means that it's possible that Fabric is having difficulties displaying the information correctly. The issue is that I'm unsure if making changes to the pipeline and saving it means saving the Copy activities with empty definitions hence I always just repopulate them before saving. But this could be an annoying issue down the as pipelines grow more complex or layer over others. Does anyone else face the same problem? 

[Anonymous]

Hi @scca ,

Based on your description, I understand that you are currently facing an issue - the dynamic content in the copy activity is displayed as empty in the UI, even though the activity executes correctly. This may indeed be a display issue with Fabric.

I found a case with a similar issue to yours:

Bug: COPY Activity Additional Columns not populati... - Microsoft Fabric Community

First, make sure your Microsoft Fabric environment is up to date, as updates usually fix such display errors.

Can you reconfigure the copy activity of the pipeline to confirm whether the error can be reproduced?

Regarding Fabric's copy activity, you can check this document:

How to copy data using copy activity - Microsoft Fabric | Microsoft Learn

Finally, continue to monitor your pipeline closely and make sure your jobs produce the expected results.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[scca]

The behaviour remains despite results showing as expected (given that I have reconfigured the Copy activities). I would not revisit those copy activities again unless I'll be making changes to them, otherwise seeing the same issue means I'll probably have to reconfigure all copy activities that are showing up that way to have that peace of mind.