Ah, got you ('which', i/s/o 'how many'). Sorry, wrong end of stick...
No, sorry. Bear in mind that if we made it possible to list actual files in the body, there could (for some people if not you) be thousands of them. Cue potential instant overload of mail servers (and possibly our mail component, for all I know), possibly meaning the more errors there were, the less likely you'd get a warning![:shock:]( "Shocked")
.
If you need the per-file details, you need the log. Remember you can suppress detail of successfully copied files (also skipped files), so the log only shows the summary page & any errors, warnings, etc (assuming you're using HTML). Bear in mind you can compress such a slimmed-down log into a single Zip (it compresses very well) for attaching, and would only need to extract it if the body counters showed 'something to investigate'
Otherwise you'd need to rely on just a custom body showing the count (with no log mailed), and manually investigate the log if the count is non-zero (maybe remote in and read it, etc, if you have that access)
No, sorry. Bear in mind that if we made it possible to list actual files in the body, there could (for some people if not you) be thousands of them. Cue potential instant overload of mail servers (and possibly our mail component, for all I know), possibly meaning the more errors there were, the less likely you'd get a warning
. If you need the per-file details, you need the log. Remember you can suppress detail of successfully copied files (also skipped files), so the log only shows the summary page & any errors, warnings, etc (assuming you're using HTML). Bear in mind you can compress such a slimmed-down log into a single Zip (it compresses very well) for attaching, and would only need to extract it if the body counters showed 'something to investigate'
Otherwise you'd need to rely on just a custom body showing the count (with no log mailed), and manually investigate the log if the count is non-zero (maybe remote in and read it, etc, if you have that access)