Using WatchDirectory Pro 4.9.5.

I am trying to rename a file. I have monitored a network UNC and will be placing the file in the same location for archiving. In the Rename plugin, my Move to Filename is set to {monitoreddir}\{filename}. When looking at the example option, the After Move field does not show the correct location and ignores the UNC. When looking at the history, the dynamic naming of the file works, but the location does not. The network server and share are dropped.

Should the {monitoreddir} tag expand to \\server01\Reports\SuperCat? (The actual server is obviously redacted in my images but \\server01 will do in my examples.)

Did I find a bug or am I using this completely wrong for UNCs?

-Chris

---

The {monitoreddir} does not include the drive or UNC.
You can either hardcode it (\\server01\reports\{monitoreddir}\) or, I think, use {drive}.
See https://www.watchdirectory.net/wdhelp/plugins/dynamicname_functions.html

Thank you. I will hardcode.

I do feel that there is still a bug in the way the dynamic naming examples are shown. If "\\server01\Reports\SuperCat\products.csv" is entered into the "Original File" field, shouldn't {drive} expand to "\\server01\Reports" in the "After Move" field? UNCs do not appear to be handled correctly in dynamic naming. Same with {monitoreddir}. I am using the example to ensure I have the correct dynamic naming commands before testing.

I would rather use the dynamic naming than hardcoding but will do so to circumvent any issues with the UNC handling.

---