I need my workflow to move library documents into a folder in the same document library. I can copy items, then delete the original item. I'm not seeing how to specify a folder or sub-folder, just the list itself. I'm just not seeing it (therefor it is probably right in front of my nose!)
If you use SharePoint 2010 designer, you can try to use this activity.
I know this is an old thread, but after spending a good while looking about I found an OOTB SharePoint Designer 2010 solution for this problem.
To move a document to a different folder
- create an SPD2010 workflow and use the Update Item action to change the path and name of the document.
- After inserting the update list item action click on the
"this list"link and set the dropdown to
- Then click Add, select the
"Path and Name"field click on the
"...", type in your folder name followed by a
- then click
"Add or Change Lookup", select
Current Itemas the data source and the field as Name.
- The stringbilder should then show
yourfoldernameis relevant to the library root). Click OK and publish the workflow in the normal way.
- When you run the workflow it will move the doc to the specified folder.
Many thanks to Move items into a SharePoint list folder for this solution.
I don't understand why there is so much confusion about how to implement a custom workflow action (I'm confused as well). I found numerous guides on how to do this and they all required deployment to the GAC and registering smart controls in the Web.Config. I couldn't get this to work. Then I found a blog with steps on how to implement a custom action in a sandboxed solution (preferable for me anyway) and it was easy peasy. I created a workflow that takes an input parameter for the folder path from the workflow designer and moves the item to the folder. This thread is old, but I just want everyone to know this is super easy as a sandboxed solution. I used the below guide and just added my logic for moving to a folder. I recommend creating a list receiver that moves the items to a folder first because troubleshooting a list receiver is a thousand times easier than troubleshooting a workflow. So, validate your code in a list receiver then add it to the workflow based on the guide below.