Vadim Tabakman

Thanks to some amazing people that I work with (Blake Nussey, Jarad Smith and Andrew Jolly), I was finally able to get the process of moving a document to another library or document set and preserve it's version number and history.  It was no small feat. I think just to get it to work once, it took me about 26 times to publish the workflow.  Mostly, it was my own fat fingers and having spelling mistakes or uppercase when lowercase was needed (or vice versa) etc.

Often, when workflow designers (humans) need to move a document in SharePoint via a workflow, they will perform a Copy of the document and then a Delete of the original.  The problem with that, is that all version history is lost.

My colleagues pointed me the SharePoint author.dll.  You can use the Web Request action in Nintex Workflow to make an RPC call (POST) to it, specifying the Move Document command. http://msdn.microsoft.com/en-us/library/ms440627.aspx

Problem

The following actions will copy a document, but not preserve the versions or version history:

Copy Item

Copy to SharePoint

Call Web Service -> Copy.asmx

The aim here is to move a document and preserve that information.

Solution

What we can do, is call the author.dll "Move Document" using the Nintex Workflow Web Request action.

In the example I have, I'll be moving a document from one document set, to another document set.

My Source document library has 2 document sets.  Inside DocSet is a document named aaa.txt.

Source Library

I've put an "Initial.txt" file into root of this library.  I will then run the workflow on this file.

Looking at the DocSet, you can see there is a single file in there "aaa.txt" and it is on version 3.0.

DocSet

The goal is to move this document to DocSet2 and preserve the version and the version history.

Content Type: application/x-www-form-urlencoded

Headers

X-Vermeer-Content-Type - application/x-www-form-urlencoded

The message that is being sent to the author.dll is the following:

method=move+document:14.0.2.5420&service_name=/&oldUrl=Source/DocSet/aaa.txt&newUrl=Source/DocSet2/aaa.txt&url_list=[]&rename_option=findbacklinks&put_option=overwrite,migrationsemantics

The service_name is the site.  My site is the root site, so it's just a forward slash /.

oldUrl is the library/docsetname/filename

newUrl is the same format as above.

The rest we leave to the reader to investigate : http://msdn.microsoft.com/en-us/library/ms440627.aspx

When we run the workflow, the document now moves to the second document set "DocSet2".

DocSet2

If you click on the document and look at the version history, you'll see all the versions and the comments that were put in.

Version History

The Web Request action looks like this:

Web Request

 

Conclusion

What would be good, is to make this into a User Define Action and make it reusable.  If I have time, I'll try to do that.

Downloads

Posted by Vadim Tabakman Monday, July 2, 2012 11:29:00 PM Categories: Nintex Nintex Workflow Versions Web Request
Copyright Vadim Tabakman
Rate this Content 7 Votes

Comments

Thursday, July 12, 2012 12:39:39 AM
unknown

re: Nintex Workflow - Move Documents and Preserve Version History

what about list items?

Thursday, July 12, 2012 1:04:06 PM

re: Nintex Workflow - Move Documents and Preserve Version History

I'm afraid I haven't figure out how to do this with list items.  Hopefully one day :)

Friday, January 18, 2013 4:02:16 AM
unknown

re: Nintex Workflow - Move Documents and Preserve Version History

Bingo.. Commission is in the mail :)

Monday, January 21, 2013 7:34:10 PM
unknown

re: Nintex Workflow - Move Documents and Preserve Version History

This is exactly what I want to do, but I can't figure out how to get it setup.  Where is the screen "Configure Action - Web Request"?  Any further hints to set this up would be much appreciated!

Wednesday, January 23, 2013 2:43:26 AM
unknown

re: Nintex Workflow - Move Documents and Preserve Version History

did you try to request a https site content,  i have a problem to access https site;

Wednesday, January 23, 2013 12:44:05 PM

re: Nintex Workflow - Move Documents and Preserve Version History

No I haven't tried with a SSL site.  I don't have one available to test it out on, sorry.

Thursday, February 21, 2013 10:03:55 AM
Tim

re: Nintex Workflow - Move Documents and Preserve Version History

Thanks for posting this! very usefull! Do you know if it possible to use this method and move files cross-site?

 

Thursday, February 21, 2013 10:07:37 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Tim,

I'm not 100% sure, but I think it would work as long as the credential you use were for a user that had permissions to both locations.

cheers,

Vadim

Monday, February 25, 2013 6:26:28 PM
Tim2

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

When using author.dll to move a document between libraries the "modified by" property for all versions of that document changes to the user credentials passed in the Web Request.  I am attempting to preserve these details and I beleive that the put_option "migratesemantics" is supposed to acheieve this.  Although, I have not been successful in my attempts.   Do you have any suggestions on what I might be able to do (or use in place of).

Tim

Tuesday, March 5, 2013 8:53:17 AM
Gman

re: Nintex Workflow - Move Documents and Preserve Version History

Excellent job, Vadim. Aside from the Document Set, can the move function be applied in 2007?

Tuesday, March 5, 2013 12:53:09 PM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi gman,

I believe it should be possible in NW2007 also, since SharePoint 2007 has an author.dll also.

I haven't tried this though :).

cheers,

Vadim

Thursday, April 11, 2013 8:51:12 AM
Stuart Moore

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

I have attempted to use this workflow to move a file from one library to another on the same site, changing your oldurl and newurl values for Site\Library\DocName of my own, but although it completed without error.  the file does not actually get moved.

I have permissions on the sites and libraries.

Any idea what I could be doing wrong

Thursday, April 11, 2013 8:57:22 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Stuart,

try changing the url in the web request to point to the destination site. Maybe that will help.

cheers,

Vadim

Monday, April 15, 2013 3:21:52 AM
unknown

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim

I am still having problems with the document not being moved, yet no error occurring and the workflow status returning Completed.

I am not using document sets, just 2 identical document libraries on the same site

I have the document I want to move in a library at the following location

IntranetHomeSite/DepartmentSubsite/TeamSubsite/ProjectSubsite/

My Source Library is called ItemsIn

My Destination Library is ItemsOut

Web URL in the request is set as

http://IntranetHomeSite/DepartmentSubsite/TeamSubsite/ProjectSubsite//_vti_bin/_vti_aut/author.dll

The message that is being sent to the author.dll is the following

method=move+document:14.0.6029.1000&service_name=http://IntranetHomeSite/DepartmentSubsite/TeamSubsite/ProjectSubsite/&oldUrl=ItemsIn/aaa.txt&newUrl=ItemsOut/aaa.txt&url_list=[]&rename_option=findbacklinks&put_option=overwrite,migrationsemantics

Any assistance you can provide would be extremely useful

 

Monday, April 15, 2013 7:38:04 AM
unknown

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

I've solved my issue, looks like it was simply a case of fat finger.

Is there a way this process could work if the source and destination libraries were in different sites (one being a subsite of the other)

Tuesday, August 6, 2013 3:25:42 AM
Stevo

re: Nintex Workflow - Move Documents and Preserve Version History

Hi, with following code, I receive strange response, any idea?

method=move+document:14.0.0.6123&service_name=http://page/BUClinicsDocs/HLCDubai/&oldUrl=Documents/Test/Test.doc&newUrl=Documents/Test1/Test.doc&url_list=[]&rename_option=findbacklinks&put_option=overwrite,migrationsemantics

My response always Shows following:

Response status code: 200

Response content: <html><head><title>vermeer RPC packet</title></head> <body> <p>method=move document:14.0.0.6123 <p>status= <ul> <li>status=1966082 <li>osstatus=0 <li>msg=Access denied. <li>osmsg= </ul> <p>message=could not rename URL 'Documents/Test/Test.doc' as 'Documents/Test1/Test.doc' <p>oldUrl=Documents/Test/Test.doc <p>newUrl=Documents/Test1/Test.doc </body> </html>

Response headers: Connection=close Content-Type=text/html; charset=utf-8 Date=Tue, 06 Aug 2013 09:23:02 GMT Server=Microsoft-IIS/7.5

Response cookies:

 

Tuesday, August 6, 2013 4:50:54 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi stevo, is it possible you already have a document in test1 with the same make? Cheers Vadim
Tuesday, August 6, 2013 5:09:55 AM
Stevo

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim, thx for you fast response, after changing my credentials the "Access denied" is gone but following appears, and NO there is no doc in Test1, what do I wrong with the paths?

URL: http://intranet.medel.com/BUClinicsDocs/HLCDubai/_vti_bin/_vti_aut/author.dll

method=move+document:14.0.0.6123&service_name=http://intranet.medel.com/BUClinicsDocs/HLCDubai/&oldUrl=Documents/Test/Test.doc&newUrl=Documents/Test1/Test.doc&url_list=[]&rename_option=findbacklinks&put_option=overwrite,migrationsemantics

Result:

Response status code: 200

Response content: <html><head><title>vermeer RPC packet</title></head> <body> <p>method=move document:14.0.0.6123 <p>status= <ul> <li>status=131093 <li>osstatus=3 <li>msg=Cannot open &#34;Test.doc&#34;: no such file or folder. <li>osmsg=The system cannot find the path specified. </ul> <p>message=could not rename URL 'Documents/Test/Test.doc' as 'Documents/Test1/Test.doc' <p>oldUrl=Documents/Test/Test.doc <p>newUrl=Documents/Test1/Test.doc </body> </html>

 

 

Tuesday, August 6, 2013 9:58:23 AM
Stevo

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim

Finally I did it, was a Problem of wrong paths, but there is another questions:

How can I integrate the paths with "References", [FileData] seems to Play a role???

Any ideas?

Saturday, August 17, 2013 9:23:57 AM
Alex

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim. I join to Tim question about changing 'Modified by' property in version history after document has been moved. Is it possible to preserve this information?

Wednesday, August 21, 2013 7:05:06 AM
Andy

re: Nintex Workflow - Move Documents and Preserve Version History

Hi, Thank you Vadmin, this was exactly what I needed. Works for moving between librarys too.

But I join in on the 'Modified by' property problem. I looked up the put_option Parameter in the documentation, it says:"The user must have administrative permissions or migrationsemantics is ignored"

Dose It mean I need to have administrative permissions on the Server not just the siteCollection? To bad my admin is on vaccation.

@Tim & Alex, you seem to be having the same problem, did you find a solution?

Tuesday, September 3, 2013 3:23:09 PM

re: Nintex Workflow - Move Documents and Preserve Version History

Hey Vadim - any thoughts on best practices for list items in terms of this request?

At my clients office, a good majority of the workflow requests we get have to deal with approval processes. 90% of the time I hear that after the request has completed, it should be locked down. For most situations this is ok, but for heavily used workflows I'm not sure how to handle this request. On one hand, we could get into an ACL nightmare and start to affect farm performance if I leave unique permissions. I like to move things to secured folder or list and cut it down to a single ACL. The huge issue with this is I lose all metadata, including versioning and just as important, workflow history!

For library items, I can use this method (thanks!!). For lists, which are more typical than libraries, I'm stumped. I have to evaluate which is the lesser evil on a case by case basis which tends to leave my client feeling less than satisfied, but I can't figure out a good end-all approach to this. I've tried researching if this is even possible (taking Nintex out of the equation), and it looks like it might not be unless we get into PS, which is obviously not a good solution when they have well over 500 active workflows.

Just wondering if you had any insights on this one :)

Thanks Vadim! Hope all is well and congrats on your new role.

-Josh

Thursday, September 5, 2013 2:27:52 PM

re: Nintex Workflow - Move Documents and Preserve Version History

Hey Josh,

A little while back I tried to figure this out for List items but wasn't very successful.  You should see my todo list now!! haha.

I wish I could point you in the right direction.  My next step was going to look into any code I could try to move items around and preserve the history.  I haven't found much yet, but haven't spent much time on it.

Vadim

Thursday, September 5, 2013 4:13:06 PM

re: Nintex Workflow - Move Documents and Preserve Version History

No problem Vadim, thanks for the reply! I'll let you know if I find anything in my quest :)

Take care,
-Josh

Friday, September 6, 2013 12:45:06 PM
Matthias

re: Nintex Workflow - Move Documents and Preserve Version History

Hi everyone, 

I am also trying to get the "Modified Property" issue to work. Tried various "administrative" accounts but nothing seems to get it to work. 

Tim,Alex, Andy: Any success on your and? 

cheers,

matt

Monday, September 16, 2013 3:22:48 AM
Andy

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Matt,

no, no luck so far. I'm using a system account now, and I added a custom column that I use to store the last Person who actually changed something.
It's not pretty but all the versions are now "modified by" system account and since the change in the custom column shows up in the version history too, it is possible to find out who actually modified the document.

I'm still checking this page once or twice a week to see if somebody else found a better solution.

Monday, September 30, 2013 12:25:38 AM
Matt

re: Nintex Workflow - Move Documents and Preserve Version History

Hi everyone, 

it seems to me (after a lot of digging) a limitation by SharePoint. If you try to move the document using the workflow above inbetween one doc lib  to different folders the put_option is working as expeceted. As soon as you leave the "scope" of a document library the issue with the system account starts to appear. 

So a possible workaround would be to redesign your application to use folders instead of libraries (that's what I did at least). For most possible scenaries it should be possible as the most important thing (permissiosn) can be set on folders or doc libs identicially and everything else should also be possible to be worked around. 

cheers,

matt

PS: If I am reading the original post correct Vadim was also always working withing one doc lib...

Friday, November 15, 2013 8:32:50 AM
NJ Lech

re: Nintex Workflow - Move Documents and Preserve Version History

To contribute to this thread and expand on what Matt is saying...

I recently did some testing to move a document from one library to another library on the same site and found these results:

As long as the source library name/path, destination library name/path, and doc name is correct in the Web Request action, the document will be moved with all the correct version history (meta data/ content type info) from the original document.  However you cannot see the field changes at a glance when you look at Version History panel for that item after it is moved.   You will also not be able to see version history if you click the dropdown and select View for any previous version in the Version History panel.  

All you can see is a listing of all previous versions with version number (0.1, 0.2, 1.0, 1.1, or whatever), the date it was modified, Modfied by, the file size, and any Comments per previous version.  But if you click the dropdown and select Restore on a particular previous version, it will restore the field changes you once had, and you will see that all the field history has been preserved.  

What makes it difficult is that you cannot see the individual field changes in the Version History panel per previous version number AFTER the document has been moved, like you can see in the Version History panel before the document was moved.  So, it looks like the version history was not preserved.   But the important thing is that the version history does indeed stay intact, for each individual version.  Vadim mentioned to me that it looks like a deficiency with Sharepoint.  But as far as I know, there is no resolution or workaround at the moment.

I hope this helps.

Wednesday, January 22, 2014 5:19:44 AM
Chris

re: Nintex Workflow - Move Documents and Preserve Version History

Thanks Vadim (and subsequent contributors) - just what I was looking for and got it woking in SP2007 for most documents. However, I am having a problem with certain 'documents'. There a number of emails stored in the source document library as .htm files. I have checked that the workflow is picking up and using the correct document name,  but the web request is simply not moving the item. I presume that this is to do with the particular file type. Is there anything I can do to get this working, either within the workflow to manipulate the item name value, or within my SharePoint configuration so that .htm files will get moved? Thanks, Chris

Wednesday, January 22, 2014 8:29:57 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Chris,

although I haven't tried this, I think it's definitely worth trying to rename the file before running the Web Request action, just in case it is the filetype.

Hope this works.

cheers,

Vadim

Friday, February 7, 2014 1:43:57 PM
Bill

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

 

I wonder if you could help me with this workflow error.

I'm suing an exact copy of your tutorial and I get an error while trying to copy a document from one library to another.

This is the error message: "Invalid URI: The format of the URI could not be determined."

this the example I used:

 

method=move+document:14.0.2.5420&service_name=/&oldUrl=sites/sop/External%20Documents/1111.pdf&newUrl=sites/sop/Archive%20External/1111.pdf&url_list=[]&rename_option=findbacklinks&put_option=overwrite,migrationsemantics

Your help is greatly appreciated.

Bill

 

Wednesday, May 7, 2014 5:22:12 AM
Chet
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

 

This works great when copying to a library in the same site, however I was unable to copy to an identically named library on a subsite due to the error below

• status=131098
• osstatus=2
• msg=Folder "Certificates" does not exist.
• osmsg=The system cannot find the file specified.

 

I then created a new library in the same site as the source and was able to move the document and version History was preserved, however the  "modified by" property for all versions of that document changed to the user credentials passed in the Web Request.which is not acceptable here. Any help please or are there any plans to include version history on a "copy" or "send to" function in future

 

Wednesday, May 21, 2014 9:26:39 AM
Jake
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

After the item is moved I am trying to start a workflow. However, when the item is moved it doesn't trigger a workflow because it isn't recognized as creating or modifying an item. Do you know of any way to get around this?

Wednesday, May 21, 2014 9:44:46 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Jake,

it's probably because the user being used is a System Account, or maybe it's just weird behavior of SharePoint when you move a document this way.

You could look at after the move, use a Call Web Service action to call the Nintex Workflow web service. It has a StartWorkflow web method you could use.

cheers,

Vadim

Tuesday, May 27, 2014 7:07:49 AM
Patrik
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Thanky you! It is very helped me.

Saturday, June 14, 2014 9:15:02 AM
Umair.
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hello Vadim Tabakman,

I am having this isue "URL http://ausdrill:1001/MGMT/TestWFDocumentLibrary/Temp.docx' as 'http://ausdrill:1001/MGMT/TestPublishedDocument/temp.docx'"

My site URL is http://ausdrill:1001/MGMT/ 

My old library URL is http://ausdrill:1001/MGMT/TestWFDocumentLibrary/Temp.docx

New URL is http://ausdrill:1001/MGMT/TestPublishedDocument/Temp.docx

and this is the string is am building.

method=move+document:14.0.2.5420&
service_name=/&
oldUrl=http://ausdrill:1001/MGMT/TestWFDocumentLibrary/Temp.docx&
newUrl=http://ausdrill:1001/MGMT/TestPublishedDocument/Temp.docx&
url_list=[]&
rename_option=findbacklinks&
put_option=overwrite,migrationsemantics

Error Message is

------------------------------------------------------------------- 

Response status code: 200 Response content:
method=move document:14.0.0.7015

status=
•status=589936
•osstatus=0
•msg=The file or folder name "/MGMT/http://ausdrill:1001/MGMT/TestPublishedDocument/temp.docx" contains invalid characters. Please use a different name. Common invalid characters include the following: # % & * : < > ? / { | }
•osmsg=

message=could not rename URL 'http://ausdrill:1001/MGMT/TestWFDocumentLibrary/Temp.docx' as 'http://ausdrill:1001/MGMT/TestPublishedDocument/temp.docx'

oldUrl=http://ausdrill:1001/MGMT/TestWFDocumentLibrary/Temp.docx

newUrl=http://ausdrill:1001/MGMT/TestPublishedDocument/temp.docx Response headers: Connection=close Content-Type=text/html; charset=utf-8 Date=Sat, 14 Jun 2014 14:58:48 GMT Server=Microsoft-IIS/7.5 Response cookies:

------------------------------------------------------------------------------------------------------------------------

I am unable to figure out what I am doing wrong. Your guidance will be much appreciated.

Cheers,

Umair.

Wednesday, August 13, 2014 12:37:17 PM
Alison
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hey Vadim,

I am trying to use the author.dll move a document between two document libraries on the same site.  Below is the syntax that I am using within the web request action.  The user that I am using has farm administration rights.  The file moves but the "Modified By" metadata in the version history changes.  Is this the expected functionality?

method=move+document:14.0.7106.5002&service_name={Common:WebUrl}&oldUrl=fn-Replace({Common:ListName}," ","%20")/fn-Replace({ItemProperty:FileLeafRef}," ","%20")&newUrl=fn-Replace({Common:ListName}," ","%20")%20Archive/fn-Replace({ItemProperty:FileLeafRef}," ","%20")&url_list=[]&rename_option=findbacklinks&put_option=migrationsemantics

 

Thanks,

Alison

Sunday, August 17, 2014 8:44:51 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Alison,

I've done some tests around this and I believe that is expected behavior.  The modified fields are updated because you are moving the document.  All the other fields should remail the same.

cheers,

Vadim

Tuesday, August 26, 2014 2:18:21 AM
Thorsten
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

i have the same problem like Umair. I can´t find the problem. Do u have any idea?

thx

Thorsten

Tuesday, September 16, 2014 3:23:40 PM
Elissa
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

I am getting an error message. Any help/advice is appreciated. 

"Error performing web request. The server committed a protocol violation. Section=ResponseHeader Detail=Header name is invalid"

In the configure action I have:

Header Name = X-Vermeer-Content-Type , Value =application/x-www-form-urlencoded

method=move+document:14.0.2.5420&service_name=/&oldUrl={WorkflowVariable:sourceURL}&newUrl=
{WorkflowVariable:destinationURL}&url_list=[]
&rename_option=findbacklinks&put_option=overwrite,migrationsemantics

 

 

Tuesday, September 16, 2014 11:31:38 PM

re: Nintex Workflow - Move Documents and Preserve Version History

Hey Elissa,

do you get the same issue if your lick Run Now in the Web Request action?

Make sure you replace the variable with real values before your click Run Now to see if it works or not.

Did you try the workflow attached to this post?

cheers,

Vadim

Monday, September 29, 2014 1:56:11 PM
Atul S
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

I wonder what am i doing wrong.

i get following message - "Error performing web request. The underlying connection was closed: The connection was closed unexpectedly."

i tested the account and result came back OK. i am using 15 hive so my version is 15.0.4454.1000

 

 

Friday, October 3, 2014 8:19:38 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Atul,

I'm afraid I don't know what is causing that.  I've never encountered that error.

cheers,

Vadim

Wednesday, November 19, 2014 7:30:47 AM
Kael
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hi everybody!

I really need this information, but for an item!

I want to create an UDA for moving an item in a folder of the same list.

Do you have some news about "moving items and preserve version history"? :D

Thank you very much in advance and have a nice day!

Kael

Wednesday, November 19, 2014 8:33:10 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Kael,

I haven't found a way to do this yet.  Hopefully, someone else has and can shed some light on this.

cheers,

Vadim

Tuesday, September 29, 2015 12:44:13 AM
Stefano De Pecol
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hi!

I've implemented the Nintex Workflow 2010 Web Request action as described, but I faced some issues:

  1. the parameter "put_option=migrationsemantics" requires that the action is executed by an initiator with Full Control permissions (administrator)
  2. if you want to copy the version history, you have to 'move' the item, not 'copy' it (i.e. you should NOT use the parameter "docopy= true")
  3. even with the a.m. points fulfilled, I'm still not able to copy the whole item version history, I mean, I missed the 'description' text of each copied version: I get only the version number, the 'modified' and the 'modified by' info.

Where did I go wrong?

Did I miss something?

Thanks.

Stefano

Wednesday, September 30, 2015 12:15:26 PM

re: Nintex Workflow - Move Documents and Preserve Version History

I don't know what you did wrong.  But did you try the workflow I have in the download section?

Vadim

Thursday, October 1, 2015 8:24:44 AM
Stefano De Pecol
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

 Hi Vadim.

Thank you very much for your prompt reply.

Yes, I've imported and test it, but I've got the same results (I can send you a Word document with snapshot of the version histories, before and after moving the document).

Thank & Regards

Stefano

Friday, October 2, 2015 9:01:22 PM
Don Harman
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Vadim,

I am using this workflow to move documents that arrive in doc library A  from a Kofax scanning workflow. I then move them to the Library B. All works fine when I upload an item the workflow runs fine.

However it does not get triggered as it arrives in Lib A using the System account.. Any ideas on how to get around this?

 

Many thanks

Don Harman

Friday, October 2, 2015 11:06:20 PM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Don,

SP doesn't kick off workflow automatically if the initiator is a system account.

You could consider uploading the document as another account, or otherwise, have a scheduled workflow that runs periodically and when it finds new documents, it starts a workflow on them that does the move.

cheers,

Vadim

Thursday, May 19, 2016 9:38:46 PM
Julian Nye
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

I'm trying to move files across sites using this method, however I've come unstuck with formulating the new url.

What I have is :

&newUrl=fn-Replace("https://blahblahblah/sites/bt-apps-os/"),"/","%2f")TestArch/fn-Replace({ItemProperty:FileLeafRef}," ","%20")&url_list

 

however, I get the following error message:

Error performing web request. The server committed a protocol violation. Section=ResponseHeader Detail=Header name is invalid

Are you able to advise what I'm doing wrong??

Kind regards

Julian

Thursday, May 19, 2016 9:43:15 PM
Julian Nye
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

sorry missed a bit off the end of &newURL, should be:

 

&newUrl=fn-Replace("https://teams.at.govt.nz/sites/bt-apps-os/"),"/","%2f")TestArch/fn-Replace({ItemProperty:FileLeafRef}," ","%20")&url_list=[]

Thursday, June 9, 2016 2:45:24 PM
Vignesh Natarajan
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

 

Greetings! I am looking a similar idea like this where i want to copy a list item instead of document. Is there any way we can copy a list item with version history.. because we have a multi lines of text field in the source  list. when we simply copy the item, it only shows latest value of the mulitiple line field. so the other lines of its initial version of the item are not getting copied.

Will be very happy if i get back from you..

thanks,

vignesh Natarajan

Thursday, June 9, 2016 2:52:22 PM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vignesh,

I'm sorry, but I've never figure out how to do this with a list Item.

Vadim

Friday, June 10, 2016 7:24:14 AM
Vignesh Natarajan
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Vadim,

Thats very sad.  :-( I will tell you if I figure out.. Anyway thanks..

Thursday, June 16, 2016 7:47:45 AM
Catharine
Gravatar

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Vadim,

This has been really helpful - thank you.  But I have a strange symptom. 

I am trying to move a document from one library to another in the same site, which we are designating as an archive. 

Both document libraries have many content types associated with them.  When uploading a document to this origin library, content organiser rules control which folder the document is stored in.  No content organizer rules point to the archive document library.

I am testing on a couple of documents,  the results of the web requests both appear successful,

message=successfully renamed URL 'SADAllDocuments/CVWTest1.docx' as 'SADArchive/CVWTest1.docx and message=successfully renamed URL 'SADAllDocuments/CVWTest.docx' as 'SADArchive/CVWTest.docx

When I look in the Archive library (SADArchive) the documents are not present.  And when I go to the origin (SADAllDocuments) library the documents are in the root with new modified by/modified data. 

I have tested this several times.  If my original document is in a sub folder, after the web request has been performed it is moved to the root of the origin library.

Any ideas ?  Could the content organizer be causing a problem ?

Thursday, June 16, 2016 8:06:24 AM

re: Nintex Workflow - Move Documents and Preserve Version History

Hi Catharine,

in the message, are you putting in the document library name and the folder it's meant to go in to?

eg

'SADArchive/subfolder/CVWTest1.docx' ?

 

Vadim

You must sign in to this site to post comments.
Already Registered?
Sign In
Not Yet Registered?
Register





 

Statistics

  • Entries (272)
  • Comments (1768)

Categories