Using Run Command Tool To Create New File When The File is Actively in Use

[dougop]

Hello,

I am working on trying to update a WF to be able to utilize an input file even when it is opened by another user.  There are instances when the WF needs to run but there is also another user in the input file working.  I have the attached WF in which the run command works when I am not in the original file, but I get the attached screenshot error when I am in the original file that is being copied/renamed.  I have also tried the blob method, but same thing... works when I am not in the original file but errors like a normal WF does when I am in the original file.

Any suggestions on how best to solve the issue?  

[jrlindem]

I have solved for this before.  My scenario was using an excel file that could be in-use by someone else.  What you can do is use the run command and "copy" the source file.  This will copy it as it was last saved regardless of it being open.

Then you can paste that file (using same run command) into a temp location and call for that new copy in your workflow to process the data.  Sequence these steps using block-unitl-done or control-containers.  Once done, dump the copy (optional).

Give that a try,  -Jay

[dougop]

Yea the attached Workflow above is what I have so far (I took out the actual folder pathways I was using and put in dummy text.  I.e. "your folder pathway here") when I have it actually set up with the real folder/file pathways the WF correctly works where it copies the file with the new name in a different folder.  However it only works when someone is not in the file, so I am wondering if it is something with how the run command tool I have on there is set up?

[jrlindem]

@dougop Hmmm, that's not been my experience.

I have had some situations where different folder permissions between myself and the user with the file open have caused some issues.  In that case I used robocopy instead of copy, but I don't see any glaring issues with your workflow that would prohibit this from being successful.  Are you confident the issue is the COPY and not the REN (rename) pieces?

Your command may be trying to rename the file before it's fully copied.  Try isolating down just the copy pieces and if you need to rename do it further downstream in your workflow; again with a block-until-done and/or control-container and see if that works.