Share Point Online Credentials($User Name,(Convert To-Secure String $Password -As Plain Text -Force)) #Set up the context $Context = New-Object Microsoft.
Recently, in one of my projects there was a requirement to create a Share Point list workflow that triggers when an item is created, and that should result in creating a new list item on another Share Point list which is created on some other Share Point instance.
When the update is performed the new or existing List item ID will be returned to Think Automation.
The only field I was updating in my list was Title.
The Tactic ID and Record ID do not change after creation.
This source doesn’t contain the unique ID for the list item, since that ID is unique to Share Point.
In my example below I have a CDS entity called Tactic.
In order to update a Share Point list item, you must have the unique ID, even if there are other fields that are unique to the item.
I spent a while searching through forums to find out how to accomplish this, so I’m documenting it here in the hopes it helps someone else.
I knew the default copy list item activity will not work in this scenario as both lists are not on the same Share Point site.
The straight forward solution to this on top of my mind was to use ‘Call HTTP Service’ activity by calling Share Point REST services with POST method, and create the item on another list.
Most examples around the internet do this by querying the list first and then getting the List Item Entity Type Full Name property from it and using that in the call to update the list items.