Requiring users to recreate an entire Copy Job just to change something as fundamental as the source connection or connection URL is unnecessarily restrictive and creates significant maintenance overhead.
A Copy Job should allow users to:
- Change the source connection
- Change the destination connection
- Edit connection details
- Repoint a job to a replacement connection
- Preserve existing mappings, scheduling, and other configuration when changing connections
Having to rebuild a working job because one connection property needs to change makes Copy Jobs much less useful for production data workflows.
Please add the ability to edit or replace connections on an existing Copy Job.
No CommentsBe the first to comment
