Is there an existing issue for this?
Current Behavior
imagine you want to change the key of a dataExtension using --changeKeyValue or --changeKeyField.
Unfortunately, the new key already existed and hence the update failed.
This should be the end of it, but our script does not realize the issue and still goes ahead and deletes the not-updated-file, assuming that a new file with the updated key will be created automatically
Expected Behavior
if update fails while running changeKeyX, the file should be be kept and not get deleted
Steps To Reproduce
- Go to '...'
- Click on '....'
- Run '...'
- See error...
Version
5.0.2
Environment
Participation
Additional comments
No response
Is there an existing issue for this?
Current Behavior
imagine you want to change the key of a dataExtension using --changeKeyValue or --changeKeyField.
Unfortunately, the new key already existed and hence the update failed.
This should be the end of it, but our script does not realize the issue and still goes ahead and deletes the not-updated-file, assuming that a new file with the updated key will be created automatically
Expected Behavior
if update fails while running changeKeyX, the file should be be kept and not get deleted
Steps To Reproduce
Version
5.0.2
Environment
Participation
Additional comments
No response