Unhelpful Error Messages

[FrostyShamRock]

I've been trying to use PA to create a flow to get details from an MS Form and add the resonses to an email. This worked previously. Now when I create it and build the email with the response options I keep getting this error:

ExpressionEvaluationFailed. The execution of template action 'For_each' failed: the result of the evaluation of 'foreach' expression '@items('Apply_to_each')?['resourceData/responseId']' is of type 'Integer'. The result must be a valid array.

This message isn't useful or helpful and results in me having to recreate the email body (which takes ages). 

Does anyone have any idea how to resolve this?  

The flow steps are:

1. When a new response is submitted (Gets details from the MS Form)

2. Get Response Details (Response ID)

3. Send an email (V2)

Note there is a holding box? that is called 'Apply to each' and in that is 'For each' where the Get response details and email body sit - I didn't put them inside 'Apply to each' / 'For each' - PA did.

[Anchov]

PA will add your actions to a For Each \ Apply to condition when it detects that the input you are giving it is part of any array.  In this case, it got it wrong and you will need to get the Get Response details out of the Apply to \ For Each actions so it is flat like this:

---

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Cheers!
Rick Hurt

[FrostyShamRock]

@Anchov, thank you for your feedback. Is there a  simple way to stop PA from adding it to the array? I've tried but it seems to do it without prompts!

[Anchov]

 Not really, its based on the input parameter you put in.  In your example, it looks like "list of responses" is being dropped into the Response Id field.  Power Automate is detecting that this is an array and therefore, putting this action in a looping action to service each object in the array:

I am not sure where the "List of responses" is coming from your screenshots, as I don't see this as an output  parameter of "when a new response is submitted" form trigger.  However, when I select ResponseId, this is seen as an integer value, and thus it is not put in a loop object:

Sometimes, when you erroneously put in an array object (or it is erroneously detected as an array), PA will "helpfully" put your action in a loop action automatically.  To correct, you have to manually drag and drop out of the loop action, add the non-array Response Id parameter, then delete the loop action(s).  I can understand this can be frustrating.

[FrostyShamRock]

@Anchov thank you for your input. As an update - I used copilot to create a new flow and it appears to overcome the array issue. The flow image is attached. However, there is another issue - I've created text for the body of the email. I use the dynamic content to pull responses from the form. When I hit save, the flow will only keep some reponses while others 'disappear'. This has been happening for the last few iterations of this flow. See the attached Gif that I took to show what is happening. I'm all about done with this as it is too frustrating and time-consuming to try to use this. PA used to work like a charm to send a summary email of the form details submitted. But I think I'll have to dump it :-(. 

[Anchov]

I encountered another user yesterday who faced the same issue, so it might be another bug in the new designer (I've run into a few recently!). My suggestion to them was to compose the email text in a Compose action above the email and then reference the Compose action in the body of the email. However, I haven't heard back if that worked for them. Another option is to try editing and saving your flow in the classic designer to see if the same issue occurs.

Original thread:
https://powerusers.microsoft.com/t5/General-Power-Automate/Cannot-include-specific-Form-result-in-em...

---

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Cheers!
Rick Hurt

[Chriddle]

This is caused by the "Split On" not activated in the settings of the trigger