Thanks for the reply.
At the time [Upload Name] is called, HFS has possibly not yet checked to see if the name will clash, and does not seem to indicate the proposed alternative name it will use.
That is, even if "filename" already exists in the current folder, so that HFS will indeed actually save the newly uploaded file as "filename (1)"; still, the %item-name% shown is merely "filename", not "filename (1)", within the [Upload Name] handler.
Is there an alternative %item-something% that gives the proposed name HFS will really use when it writes out this file?
If the "non-clashing" name is not available from HFS, then, for me to handle it means I'll need to replicate all of the logic that HFS already has in place to come up with a non-overlapping name. This seems both redundant and tricky.
I'd rather there was a way to suggest what separator character HFS should use before its added "(number)" suffix. Currently this separator is " ", and I'd prefer, say, "_" . With the change of separator character, then the existing file name code would fit my needs.
But, I guess this is not that big a deal. So, for now, I'll probably just ignore the issue, rather than implementing my own "check for duplicate file names" logic.
Thanks,
Steve