@Amanthaper
I can’t do pics right now, but the flow runs like this:
1. when a planner task is completed
2. initialize variable for the user id
3. Apply to each:
A. “Get task details” for the task completed
B. “Compose” to get the description from the planner task
C. “Get user profile (V2)” to get the if of you completed the task. This uses an expression of: item(‘Apply_to_each’)?[‘completedBy/user/id’]
D. “Append to sting variable” for the display name
E. “Get items” from a SharePoint list
F. “Apply to each”/“Condition” - does the value in the Planner ID column on the SP list match the planner task id
If yes:
1. Update the SP list item with the display name of who completed the task and the description
2. Create a new SP item on a new SP list and copy the information from the item that was updated
3. Delete the item from the first SP list.
All of the concurrencies from top to bottom are set to 1. The problem I get is that when I complete multiple tasks at the same the column where it puts the name of who completed the task gets multiple names after the first task (I.e. the first take update gets only 1 name, the 2nd task updated gets 2 names, the 3rd gets 3 names and so on). The flow works great if you’re only completing 1 task at a time, but it’s more likely that several tasks will be completed at the same time.