The easiest solution would be to use the Create Item action with the references to each field. Using the Lists web service would require knowledge of these calls and several additional actions to build the XML for the service and to consume and locate ID and URL in the XML result from the call.
It seems that you cannot use Copy to SharePoint as it only supports documents. See for more details.
I've done something similar to this by using override credentials to create the new item. (I've found that workflows wont start on items created by SharePoint.)
Then I create a separate workflow to start on item creation that updates the name and a couple of other fields for the new item. It's all within the same library and it happens almost instantly so it works well.
Thanks
Kassie
Hi Pascal
We have done something similar to this but in our case, our Title field had unique values so it was easy. When you use the 'Copy Item' action, basically it duplicates all field values to the new Item as well.
e.g. Say you have an Item with ID 100 and Title = 'ABC' and when you 'Copy Item' it creates a new Item with a different ID but the same Title
Once the new Item is created, Use the 'Query List' Action and filter Items with the Title Name = 'ABC' and Item ID <> 100 which will return you the ID of the new Item created.
Once you have the ID of the new Item, you can use the 'Update Item' action to update the newly created Item.
Will this help?
Pascal, just for my understanding, what helped in this scenario of using the Update Item action over the Create Item action?
