Word of warning:
If you need to have more than one workflow for a particular list/library, DO NOT copy a SPD workflow and paste back into the same library.
What happens is that even if you change all of the properties of the files (names, etc.), there is still a hidden property that SharePoint likes to hold on to and uses to identify the workflow. Think of it as an ID.
Basically, you will have two different workflows with the same ID. When you publish one of these to a list/library, everything works fine. When you go to publish the second one, everything seems fine but after close evaluation, you will notice that the first workflow that you published is no longer attached to the list/library.
Moral of the story, don’t be lazy. Create a new workflow even if all of the information is the same.
I was faced with this task recently. Let me paint the picture for you.
I have a document library with over 1,000 items in it. I added a new column (Named) that needs to have the same information as an existing column (Name). For whatever reason, the web part I am using for my list search does not recognize the existing column. I created a SP Designer workflow to copy the contents from the ‘Name’ to the ‘Named’ on creation or edit.
To do this, there are a couple of options.
- The long drawn out option – Edit each file individually
- The best option for me – Content and Structure
- Power option – SharePoint Designer
I went with option 2 because I did not want to lag the server with a whole lot of who ha. Here are the steps I followed to make this happen.
- Go to the site, Site Settings, Content and Structure
- Expand the library to perform this action
- Place a check into the ‘Select All’ check box
- Click on the ‘Actions’ drop down and select ‘Check Out’
- Once checked out (you may have to do this twice), click the ‘Actions’ drop down and select ‘Check In’
Make sure to check that you have performed this action for all items in your view. Mine were in groups of 100, which is generally the standard view. The fasted option for me would have been the SharePoint Designer route but I did not want to take a chance of checking out over 1,000 items at once and then check them back in. We already have enough load on the servers from all of the other users accessing SharePoint.