You cannot save after adding new tables to an existing copy task

[Jarrinf]

I wanted to add a couple of tables to my existing copy job task.  The assitant let me add the tables, configure the type of copy, configure the differential datetime field, but cannot save the changes.

I had to create a new copy job task but that first run starts the copy from the scratch with a full copy, so that is not a good option.

Any Idea?

[v-sgandrathi · Accepted solution]

Hi @Jarrinf,

This behavior is expected for Copy Job tasks in Microsoft Fabric. After a Copy Job is created and run, its configuration, including the table list is linked to the task’s metadata and incremental state. While the UI might let you add tables or change settings like copy type or differential column, saving these changes can fail because the task was set up with the original tables. So, adding new tables to an existing Copy Job isn’t fully supported in many cases.

The suggested solution is to create a new Copy Job task for any additional tables. This keeps the incremental state of the original tables unchanged. Note that a new Copy Job is treated as a separate task and will do a full load on its first run since there’s no previous watermark. If you need incremental loading from the start, you may need to set the differential column or watermark value to begin from a certain point, if the source supports it. For situations where you need to add new tables often and want more control over incremental logic, Data Factory pipelines in Fabric with a custom watermark can offer more flexibility.

Thank you.