Copy list item from one site to another including attachements

list name should have been its name (title) or GUID, not URL

Does that mean that I am only able to add attachements with this web service call within the site collection I am currently in?!

No, I don't think that's what @emha is saying. The first field you specify on the Call web service action is the URL. The listName field is just the name of the list on the site you specify in the URL field.

OK, I think I am slowly  getting there...

I now have a problem, with this line:

<m:fileName>{ItemProperty:FileLeaveRef}</m:fileName>

It seems that {ItemProperty:FileLeaveRef} is not resolved by NINTEX.....

Any ideas why?!

yes, @nj is right, site URL where do you call web service from denotes where target list is being looked for.

reg. FileLeaveRef - do you expect it contains attachment(s) name(s)? that's not the case. write it to history log to see its content.

you will have to get attachment(s) name(s) either from hidden nintex's column FormData or from sharepoint by a call to Lists.asmx webservice

Okay. So with that (web service "GetAttachmentCollection") I was able to retrieve the file names and in a second step I was  able to copy the attachments into the list. I tested it with two attachments, both were attached to the list entry I wanted.

So far so good!

BUT it seems that the files have been corrupted. What could be the reason for that?

I attached a *.txt file and a *.docx file.

Opening the copied *.txt file:

Opening the copied *.docx file:

(it says: Error opening the file in Word)

I would guess from Nintex point of view everything is configured correctly...

Cheers

mai-kel

how did you copied the content over?

have you base64 encoded it?

I used the WS "AddAttachment" with the following service message:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m="http://schemas.microsoft.com/sharepoint/soap/">
<soap:Header>
</soap:Header>
<soap:Body>
<m:AddAttachment>
<m:listName>Feedbackmanagement</m:listName>
<m:listItemID>{WorkflowVariable:lidNeueElementID}</m:listItemID>
<m:fileName>{WorkflowVariable:slotAttachmentShort}</m:fileName>
<m:attachment>base64Binary</m:attachment>
</m:AddAttachment>
</soap:Body>
</soap:Envelope>

I am pretty sure this is not working because of this line:

<m:attachment>base64Binary</m:attachment>

But I honestly have no clue what to write instead...

I have seen something like this, but that is also not working:

<m:attachment>FileData</m:attachment>

Maybe @vadim_tabakman has an idea, as he has already written some blog posts about this?!?

once again, you cannot supplie 'base64Binary' or 'FileData' literally as these string.

they are just a placeholders for real file content. and the file content has to be base64 encoded.

as you mentioned, a possible way how to get list item's attachment base64 encoded is described on Vadim's blog

http://www.vadimtabakman.com/nintex-workflow-get-list-item-attachment-in-base64-custom-action-happy-thanksgiving.aspx

which one?

none of these two links are important in your context.

anyway, nintex workflow SDK has been moved to the help portal https://help.nintex.com/Content/helpportal.htm

MS KB article showed just a sample C code how to get listitem attachemnts

https://web.archive.org/web/20150304172150/http://support.microsoft.com/kb/929259

have you read through Vadim's blog???

you do not need any coding.

simply download his GetListItemAttachemnt action suitable for your environment, ask your admins to install it, and then you can use it just like any other workflow action.

OK all,

I finally managed to copy a list entry from one site collection to another site collection including attachements. As it took me quite a while and I am happy with the solution I want to share this with you.

As a prerequisite you need to build two identical lists. One in the site collection A, second in site collection B.

Another prerequisite is to setup a document library on both site collections, I named them both "FeedbackAttachments".

Now we can build the first workflow (running on the list) of two workflows (the other one is running on the attachment folder):

1. Create element in another website (here we copy all the columns from one list to another):

2. Commit pendig changes (always a good idea after updating a list!)

3. Copy to SharePoint (here we copy the attachment to the prepared folder)

4. Regular Expression

5. For each

6. Query list

 7. Update multiple items

8. Commit pendig changes (always a good idea after updating a list!)

9. Call web service

That's all for this workflow. Now go to the folder you've created and create a new workflow:

1. Call web service

Web service message:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m="http://schemas.microsoft.com/sharepoint/soap/">
<soap:Header>
</soap:Header>
<soap:Body>
<m:AddAttachment>
<m:listName>FeedbackmanagementNeu</m:listName>
<m:listItemID>{ItemProperty:Title}</m:listItemID>
<m:fileName>{ItemProperty:FileLeafRef}</m:fileName>
<m:attachment>[FileData]</m:attachment>
</m:AddAttachment>
</soap:Body>
</soap:Envelope>

2. Delete item

BTW: as this workflow is only started be the web service call from our first workflow you can keep the settings here as follows:

That's it. Enjoy!

Cheers

mai-kel

@emha :

1. I was not able to use a WSP on customer system, but with this, it also worked

2. Luckily this "wording" does the job: <m:attachment>[FileData]</m:attachment>

@mai-kel 

I am having trouble with getting the base64 from the documents if you could help. I am able to copy the attachments from the list to the document library. Now i am calling the web service to get the base64, which i am interested in, but unable to get it. In your screenshot you have m:ListItemID as ItemProperty:Title, is this correct? or should it be the ItemID of the document in the document library for which i am trying to get the base64 for?

@mai-kel ,

Finally got this to work.