How to turn objects into array in Power Automate 2025

(0) Share

Report

Posted on by powerpepper

106

Hi all.

The solutions I've found are outdated/don't work for me.

I'm working with Power Apps and Power Automate to track tasks. When a task is marked as complete, the flow

should move it to a separate sharepoint list (completed task list). The issue is with the flow. It produced a Bad

Request error, saying the specified user could not be found. To fix, I tried turning the data field into an array.

It produced the error below.

My solution is below. However, no where does the flow indicate that an array even needs to be made, like with the

Assign to Claims - 1 field in the second picture. My first notion of copying and pasting the variable into the

corresponding field (dragging Covering for Claims variable to Covering for Claims field) should have worked. But didn't.

So, I'm at a complete lost and not sure what's wrong with this flow. I'm looking for solutions within Power Automate

only. Please and thank you for any help.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Pstork1 68,707 Most Valuable Professional on at

Like (1)

Report

If you have an object that has the right properties, but it needs to be part of an array to put in a multiselect field the easiest way to do that conversion is to create a blank array variable and then use the append to array action to append the object to the array variable. You don't need to convert the object to an array. You need it to be a member of an array of one.

----------------------------------------------------------------------------------
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! Your solution did allow me to use the object as an array, so I was able to use it in the Select operation.

Unfortunately, I'm still having trouble with this flow. It's producing the same error: Bad Request. Specified user could not be found (which I know is not true, because I'm the user it can't find). I'm mostly chucking this up to an update I some how missed (???) The flow I created weeks ago, worked wonderfully with no issues. If anyone is aware of the update (or not) and still has suggestions, I'm open.

@Pstork1 - I'll mark your reply as an answer, since it did answer my original question. I'll add any other helpful solutions too.

Was this reply helpful? Yes No