Forum Discussion
Create copy data activity from copy assistant
I've had a Fabric data pipeline for a couple of years where I create copy data activities for files periodically released to us that vary in schema, and have a large number of columns. For this reason, we would use the copy assistant to pick up the schema from each file so we don't have to manually map large numbers of columns. It appears that the copy assistant now outputs a copy job activity, which does not allow us to use variables in the file path and is much more limited in features regardless. Is there any way to force it to output to the traditional copy data activity? I can't see anything that will allow me to do this
9 Replies
Current docs on the subject are out of date and refer to the older UI experience:
https://learn.microsoft.com/en-us/fabric/data-factory/copy-data-activity
apologies I thought this was clear - I'm using data pipelines in Fabric. The copy assistant tool used to output the copy data activity, now it outputs the copy job activity, which is not fit for purpose and I can't see a way of forcing it to output the copy data activity
Hi JoshT ,
For scenarios involving dynamic or metadata-driven ingestion, the traditional Copy Data activity remains the preferred choice. At present, the new Copy Assistant defaults to generating a Copy Job activity, and there isn’t an option to make it create the classic Copy Data activity.
As an alternative, you can manually add a Copy Data activity to your pipeline and use a parameterized dataset to manage dynamic file paths and schema changes.
Regards,
Yugandhar.
H JoshT ,
Just checking in to see if you were able to share your feedback on the Fabric Ideas or Feedback forum as suggested earlier. Please let us know if you have submitted it or if you need any further assistance.
Regards,
YugandharThanks for checking. I've decided not to waste my time on the ideas forum as I've reported plenty of bugs on there and they're never picked up and nothing ever changes. I've reported bugs to service support and they've told me that clear undesirable behaviours are in fact intended by the product, so I hope you'll understand that I have no faith that the Fabric team will implement the proper development practices the rest of us are subject to. In this case I was hoping that I had missed something that would make it work, but the confirmation that the Fabric team actually decided to withdraw functionality for no good reason means I don't need any further support.
Thanks for sharing your feedback and for explaining your experience. I understand your concerns.
If you have any other questions in the future or run into something else you’d like to discuss, please feel free to reach out here in the community.
