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
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
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.
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/">
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!
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>