How to pass multiselect person data to flow & successfully move item to sharepoint list 2025

(0) Share

Report

Posted on by powerpepper

106

Hi all,

The issue lies with my "Assigned to" variable. Several weeks ago, I followed the steps in this video (posted 1 year ago) to

move the items in one sharepoint list to another. And it worked.

https://www.youtube.com/watch?v=kVrXFu_3-3Y

Today I'm following the same steps and the flow does not recognize the person data passed through it.

When using the Select operation, I even tried mapping more than the Claims field, hoping it would

align with sharepoint's/office 365's person grouping, and the flow still failed. The error comes back as

"Bad Request. The specified user {with Claims and other mapped fields} can not be found."

Does anyone have any idea why the flow does not recognize a multiselect person data and/or have a solution?

Screenshots below show the error (1), the Select/Assigned to mapping (2), and the use/output (3). Please and

thank you!

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Pstork1 68,697 Most Valuable Professional on at

Like (1)

Report

You are building Assigned to as an array since its a multiselect field, but then adding that array as though it were a single person. click on the little T icon above and to the right of the Assigned to Claims - 1 field. That will change it to accept the array.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
powerpepper 106 on at

Like (0)

Report
@Pstork1 Thank you for your patience and help,

but that didn't work.

The code showed up as it did previously.

This try and my previous tries shows the code in an

array structure (I did eventually remove the other

mapped fields to solely focus on Claims as the

video did):

[ { "Claims": [ { "Claims": "Person Info" ] } ]

So it doesn't look like pressing that button

had an impact on the code. Maybe I'm

missing something. I apologize if I am.

Was this reply helpful? Yes No
Ellis Karim 11,681 Super User 2025 Season 2 on at

Like (1)

Report
The Assigned to Claims array needs to be formatted as:

[ { "Claims": "JohannaL@onmicrosoft.com" }, { "Claims": "HenriettaM@onmicrosoft.com" }, { "Claims": "DiegoS@onmicrosoft.com" } ]

or
[ { "Claims": "i:0#.f|membership|JohannaL@onmicrosoft.com" }, { "Claims": "i:0#.f|membership|HenriettaM@onmicrosoft.com" }, { "Claims": "i:0#.f|membership|DiegoS@onmicrosoft.com" } ]

Ellis Karim
Blog | LinkedIn | Bluesky

Was this reply helpful? Yes No
Verified answer

powerpepper 106 on at

Like (0)

Report

It took several long minutes to discover my original formatting was incorrect and (going back to my original question) did not actually match the flow in the original tutorial video. So my issue came from my own inexperience, rather than the video or a missed update. 😅😂 But in my defense! being new to Power Automate (which I clearly am!) makes it very easy to overlook features that seem simple, but actually make a huge difference in how the code is being inputted and outputted by the flow. Comparing @Ellis Karim's suggested formatting with my flow's formatting, toggling on and off @Pstork1's suggested array button, and playing around with the mapping in my Select operations helped me to recognize this – thank you both!

For anyone else struggling with this (maybe you're just dragging over parameters without a second thought, like I was), follow the steps in the video. But, triple check your flow looks something like this...

GET ITEM : SETTING UP SELECT

Note: Be sure 1) From reads as Assigned to (group), 2) Map is separated into 2 columns and labeled appropriately as shown, and 3) the array button looks as it does in the image (with the "T" visible and not grayed out). Drag/drop the Assigned to (claims) into Map as shown.

CREATE ITEM : USING SELECT

Note: The parameter's name here depends on whether the array button is toggled on or off. Be sure the array button looks as it does in the image (no "T" and grayed out) and the parameter's name reads "Assigned to" and not "Assigned to Claims - 1" or something else.

If you have anything other than this, the code will not be inputted and outputted correctly and the flow will fail.

Was this reply helpful? Yes No