I’ve talked about this before, but never really got an answer, unfortunately it’s cropped up again.
Summary: It appears that when certain commands are included in a Batch file that is being executed with the “Run Program” activity, those commands are not actually being executed. When the batch file is executed manually from the command line, it works just fine.
Detail: I’ve got a very simple, one-line batch file that uses the windows XCOPY command to move a file from one network path to another:
XCOPY “\SERVERNAME\PATH\TO\FILE\TEST.XLSX” “\SERVERNAME\SHARE\POINT” /I
When running the automation script, I see the command window briefly pop open and then close, and according to the log, the command was executed.
But if I go to the remote directory - no file.
However, if I run the batch file from the command line manually, it works just fine and copies the file and creates directory(s) as needed.
Any thoughts? I haven’t tried this in TDP 3.3 beta yet, because I cannot roll beta out to production, and this is an urgent requirement from my client.