Answered

Select - Property value must be an array

(1) Share

Report

Posted on by CU02080739-1

Hi,

I am trying to create a flow using a GET request to retrieve all data via an API. I have successfully managed to return the object using an HTTP connector and the correct endpoint. However, when I try to use the 'Select' action to create a new object, I receive an error message below. Can anyone help explain this to me and the steps I need to take to resolve this? I have also tried appending the an array using variables, but I couldn't get that to work either.

BadRequest. The 'from' property value in the 'select' action inputs is of type 'Object'. The value must be an array.

Many thanks

Categories:

Building flows

I have the same question (0)

All responses (10)

Answers (1)

CU02080739-1 33 on at

Like (1)

Report
Copy link

Link copied!

Just to add that the Request returns multiple objects not just one. Not sure if that makes any difference.

Was this reply helpful? Yes No
Suggested answer

Ellis Karim 11,983 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi CU02080739-1,

Try specifying the value property of the HTTP response using an expression:

body('HTTP')?['value']

Or use the value property from the ParseJSON action in the Select action:

Ellis

Ellis Karim's Blog – IT doesn't have to be complicated!

1 people found this reply helpful.

Was this reply helpful? Yes No
CU02080739-1 33 on at

Like (1)

Report
Copy link

Link copied!

Hi ekarim,

Thanks, however I get this error new error: From Null (see below)

The Flow makes a GET request to get all major IT incident tickets through an API call. I then run parse JSON which works and returns a JSON object with all major incidents. For each ticket within the object I want to send an individual email to incident support. Below is what the Flow currently looks. Any ideas how I can get round this error?

Was this reply helpful? Yes No
CU02080739-1 33 on at

Like (1)

Report
Copy link

Link copied!

Also, just to note there is on Value property with the Parse JSON for me to select. Not sure why this would be.

Many thanks

Was this reply helpful? Yes No
Ellis Karim 11,983 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Can you please share the output from the HTTP request. For example, in my demo flow I see the body property and the value property (which is an array). Your output will differ, depending on the API endpoint you are connecting to.

Ellis

Ellis Karim's Blog – IT doesn't have to be complicated!

Was this reply helpful? Yes No
CU02080739-1 33 on at

Like (1)

Report
Copy link

Link copied!

Hi Ellis,

Thanks so much for taking the time to try and help me. Fairly new with API's at this level. Below is the output I get. I can see it does return all major incident tickets we have open.

Was this reply helpful? Yes No
Suggested answer

Ellis Karim 11,983 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
Based on the screenshot, we can see the the tickets object is an array (of ticket properties):

try the following expression in the Select action (or if you can find it, use the tickets property from the Parse JSON action):

body('HTTP')?['tickets']

Screen mockup:

Ellis

Ellis Karim's Blog – IT doesn't have to be complicated!

Was this reply helpful? Yes No
CU02080739-1 33 on at

Like (1)

Report
Copy link

Link copied!

Hi Ellis,

You are amazing! by adding: body('HTTP')?['tickets'] to apply to each seems to have worked and I can now get the values using item()?['property'] in the Select actions.

What I don't understand is why the Select action doesn't show me the tickets property after using Parse JSON. Could you explain why this happens for future reference? I run Parse JSON, add the Select action, but I don't see the tickets property available for use. I would have expected it to be an option. It would be so much easier to be able to use Parse JSON.

Many thanks for all you help so far!

Was this reply helpful? Yes No
Verified answer

Ellis Karim 11,983 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
The ParseJSON wil depend on the sample data you selected for the schema

I made up some sample data using ChatGPT and generated the following schema:

{ "type": "object", "properties": { "tickets": { "type": "array", "items": { "type": "object", "properties": { "subject": { "type": "string" }, "group_id": { "type": "string" }, "department_id": { "type": "string" }, "category": { "type": "string" }, "sub_category": { "type": "string" }, "item_category": { "type": "string" }, "requester_id": { "type": "string" }, "responder_id": { "type": "string" }, "due_by": { "type": "string" }, "fr_escalated": { "type": "boolean" }, "deleted": { "type": "boolean" }, "spam": { "type": "boolean" }, "email_config_id": {}, "fwd_emails": { "type": "array" }, "reply_cc_emails": { "type": "array" }, "cc_emails": { "type": "array" }, "is_escalated": { "type": "boolean" }, "fr_due_by": { "type": "string" }, "priority": { "type": "integer" }, "source": { "type": "integer" }, "status": { "type": "integer" }, "created_at": { "type": "string" }, "updated_at": { "type": "string" }, "workspace_id": { "type": "integer" }, "requested_for_id": { "type": "string" }, "to_emails": {}, "id": { "type": "string" }, "type": { "type": "string" }, "description": { "type": "string" }, "description_text": { "type": "string" } }, "required": [ "subject", "group_id", "department_id", "category", "sub_category", "item_category", "requester_id", "responder_id", "due_by", "fr_escalated", "deleted", "spam", "email_config_id", "fwd_emails", "reply_cc_emails", "cc_emails", "is_escalated", "fr_due_by", "priority", "source", "status", "created_at", "updated_at", "workspace_id", "requested_for_id", "to_emails", "id", "type", "description", "description_text" ] } } } }

If you can learn some more JSON, in most cases you wont need to use the ParseJSON function.

Free JSON Tutorial - JSON Crash Course | Udemy

How to Query JSON Data Using JSON Notation with Power Automate❔❔❓ – Ellis Karim's Blog

Ellis

Was this reply helpful? Yes No
CU02080739-1 33 on at

Like (1)

Report
Copy link

Link copied!

Hi Ellis,

Great, thank you for this and for the additional learning resources. Your blog is very informative and I will be following you from now on.

Many thanks!

Was this reply helpful? Yes No