This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
When I utilize your tool, the originating Directory path folder ends up being placed inside the destination path folder, along with the target file that was moved. This is in use with a Directory tool input, and defining the Destination path via a Text tool - which already has a defined target folder name that's been created in that path.
Text Tool setup - to mimic what is actually already in place in the Directory path:
@bobpeers First off just wanted to thank you for developing this tool, it was exactly the solution i needed for a recent workflow i was asked to develop. I just ran into an issue however attempting to run my workflow on the server. I had the admin install the tool on the server, however I get the error below when attempting to run it. It does run successfully on my local machine.
Should this tool be able to work on the server? I know the server service account has access to our local network share folders as i perform other actions in this main directory with other workflows on the server. Could it possibly simply the location the tool was installed on the server maybe differing from the install location on my local?