Identify of files that failed to copy?
Posted: 09 Mar 2026 18:09
The reports provided for filecopy operations are nicely detailed.
However, if the filepath(s) involved are long, the report logically uses ellipses "..." to represent that the long pathname had to be truncated.
Unfortunately, this truncation obliterates the file name and extension.
Couldn't that 'copy failed' line note the filename FIRST in the report line, and then use the ellipses to abbreviate the filepath?
After all, the user KNOWS the folder(s) involved, abbreviating the path doesn't hamstring the user, but obliterating the filename is a serious loss of information that is really NEEDED when investigating and solving 'copy failed' incidents.
Thanks.
However, if the filepath(s) involved are long, the report logically uses ellipses "..." to represent that the long pathname had to be truncated.
Unfortunately, this truncation obliterates the file name and extension.
Couldn't that 'copy failed' line note the filename FIRST in the report line, and then use the ellipses to abbreviate the filepath?
After all, the user KNOWS the folder(s) involved, abbreviating the path doesn't hamstring the user, but obliterating the filename is a serious loss of information that is really NEEDED when investigating and solving 'copy failed' incidents.
Thanks.