Run Command to Copy/Move/Rename a file

Hi Everyone,

I am having a hard time utilizing the Run Command tool to take a file on a network shared drive and copy and paste it to a new location on the network shared drive and rename it as well. Below is what I have done but the Run Command hangs indefinitely. The file I am trying to copy has 80K rows and is 1870kb in size, not sure if that is playing a part. Can anyone look at my workflow and tell me what I am doing wrong? Also, the source file I am copying has a dynamic name that will change each month and I am stripping the date from the file name when I rename it.

New Workflow1.yxmd

Datasets

Accepted answers

jrlindem

This is how I configure my Run Command. I generally always name my command line field as "Command" but I don't think that's actually necessary. Just make sure you have just one single distinct field feeding into the tool, it's formatted as something like v_string and the size of the field is 500+/- or less. Also running silent is good for when it's production, so you don't get the cmd window popping up, but I like to see it when i'm building just so I know it's working.

If you have it configured correctly, it should run very quickly.

All comments

jrlindem

I would recommend switching to robocopy syntax for your cmd: robocopy "C:\source" "D:\Destination" "file.xlsx" /MOV

I've had better luck with this when there are directory permissions that differ.

RCern

@jrlindem Would this be the correct syntax: 'robocopy' + [SourceFile] + '" "' + [TargetFile] + '"' + '/MOV'

Is my Run tool configured properly? It seems to still hang

jrlindem

Make sure you put in spaces and separate out the file for robocopy. More like:

'robocopy "' + [Source] + '" "' + [Target] + '" "' + [File] + '" /mov'

RCern

@jrlindem Thank you! How do I configure the Run Command Tool because it seems to hang/cycle? Is that due to file size and/or number of rows contained?

jrlindem

If you have it configured correctly, it should run very quickly.

RCern

@jrlindem THank yoU!

jrlindem

I wasn't able to get back quick enough to address that error... did you get it figured out? If so, what was it? -Jay

RCern

A backslash instead of a forward slash lol

jrlindem

@RCern oh gosh, sorry about that. In my haste... lol

But glad you got it sorted. Have a good weekend, -Jay

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703