Enfocus Community

It seems simple enough, but it's kicking my butt. A third party automated system is pushing files to a folder that is being monitored by Switch. There will always be three files but all three files will not be sent at the same time. I have my hold condition set properly but here's the issue. The third party automation creates the folder directory in the Switch folder, once Switch starts to monitor the folder it adds the "hidden" unique ID prefix. The Switch unique ID is not hidden to this outside software, it is seen as if the folder UNC path has changed, so it creates a new Parent folder when files are pushed. I set the folder to scan every 30 minutes, that works but on occasion the above scenario happens. If partial files were upload and then 31 minutes later the final file was sent for that job, the last file be placed in a new Parent folder.

Any ideas?

I would ungroup/split them and assemble them again based on the parent name of the folder, which Switch can do without the hidden _prefix_.

So if you have:
You would split them into the flow as separates while maintaining the parent folder name (MyJob1): And assemble them back based on that parent folder name:
Or you could, you know, have your client drop the files in a folder Switch is not watching and for-go this mess.

I was thinking of this same thing... Set a secondary hold connection to pass through folders containing less than 3 three files that has been siting for longer than 45 minutes. All file names start with the same first 13 digits. So a regroup with using the first 13 characters would be simple.

Thanks... I was looking for some magic sauce, looks like the hold connection is the best route.

Thanks for the reply.

Just if anyone cares to know. The 13 digits can be random in the file name. The files can still be combined based on those 13 digits with using [Job.NameProper:Search="([0-9]{13})"].