Showing results for 
Search instead for 
Did you mean: 

Person or Group field in item should support multiple values readable in flow


now the flow can read Person or Group field only with single person details. If its set for multiple values, the flow return null.

Would be better to read multiple values (emails for us) for case if we need to use this field for approval email on more persons.


If its problem to return all information about multiple persons, you can use setting from field, accordit what filde (ID, email, Department) will be the main, for reading in flow.


Thank you

Status: Completed

We now support multiple-valued Person and Choice fields, read more here:

Advocate II

I want to append to a multi-select Person field in an SP list.  Seems to be no out-of-the-box way of doing that.  The entire multi-select Person field is over-written.


I've tried reading the multi-select Person field into an array variable, appending to the array variable, then writing the array variable to the multi-selct Person field with "Switch to input entire array" set.  But I get bad gateway 502 on the output of the update properties ...


"error": {
"code": 502,
"source": "",
"clientRequestId": "xxx-xxx-xxx",
"message": "BadGateway",
"innerError": {
"status": 500,
"message": "Error converting value \"\" to type 'Microsoft.SharePoint.Connector.SPListExpandedUser'. Path '[0]', line 2, position 25.\r\nclientRequestId: xxx-xxx-xxx\r\nserviceRequestId: xxx-xxx-xxx"


Looks like the variable array format doesn't play well with the multi-select People filed when writing an "input entire array".


Anyone any ideas how to tweak the format?  Or is it broken?

Advocate II

Ref my comment above ... There's a solution uing the "Resolve Person" SharePoint action.


Read all of the items out of the SP multi-select Person field into an variable array, then write the person you wish to append to the SP multi-select Person field (this will over-write the multiple users already there that you want to append to, but no worries, you've just saved them into the array variable), then read the person out of the SP multi-select field again using the "Resolve Person" SharePoint action (the returned person will now have the correct format for adding to the SP multi-select Person field), append the returned person to the variable array, then write the array into the SP multi-select Person field.


The net effect is to append the extra user to the SP multi-select Person field.

Frequent Visitor

Hi Lozzie,


I was trying to achieve this by following your steps but flow is failing. Can you please post screenshots of your flow.


Thank you

Advocate II

Shot 1Shot 1


Shot 2Shot 2


Shot 3Shot 3



Frequent Visitor

Thank you Lozzie! I will test this and let you know the result

Frequent Visitor

Hello. The solution noted only lets me send emails individually rather than as one email to all "claims" individuals. It is causing me repeat emails because I have multiple columns with people to assign (ex. Assigned to, Impacted). I have tried using a semicolon or enter to place multiple users in one claims field but it comes back null. Any help would be appreciated!