Forms get response details put in for each loop

[Tomijk]

Hi,

I'm testing a flow where i write data i receive from a microsoft forms submission to an excel sheet to mutate later. In the past this was no problem but now something changed in the way I get te response details. When using the action to get the response details it is automatically put in a for each loop.

Due to this i cannot access what is inside the form response and get the following error when testing:

If i remove the for each loop to get the following flow:

I get the next error:

So i have to choose between not accessing the response, or not accessing what is in the response. Can someone tell me what i am doing wrong?

[ScottShearer]

@Tomijk 

I don't know why a loop is being added - I just tested to verify that I don't see that issue.

Can you post screen shots of the configuration of the loop and action?

[Tomijk]

Hi, Thanks for the quick reply.

For some reason i cannot replicate it now and it works as i expected. I think power automate felt that i made a post on the forum. If i get the issue again I will record my screen and post it.

[Tomijk]

Hi,

@ScottShearer 

I made a new flow and it happend again. It looks like it mostly happens with new flows but i can't always recreate it. Here is a video of what happened.

 It looks like it tries to import a list of responses sometimes?

[ScottShearer · Accepted solution]

@Tomijk 

The new interface is likely to get some updates.....

You might want to revert back to the old interface when you run into issues like this and then switch back.

[cb23]

Having this issue too! The old option to get the 'Resource ID' from the dynamic data list has changed. I tried adding an expression as the response Id instead (triggerOutputs()?['body/resourceData/responseId']) but it came back with a 'BadRequest' error message. Is this a bug? I'm not sure why it would start working in this way!

[sambg]

Switching to classic designer after selecting the form, doesn't work, you still get a for each loop being added.

Switch to classic designer before you select the form and the next step behaves as expected.

[cb23]

Ah yes, thank you. It's behaving now 🙂 

[JohnBunney]

This is happening to me as well.   Old flows are working but any new flow I create adds this loop when I request Power Automate to get the response details of the form.  I cant use the previous step to grap the Unique reponse ID only LIST OF RESPONSE NOTIFICATIONS.  Please help

[cb23]

Switch to classic designer (three dots top right) before you select the form and the next step behaves as expected.

[JohnBunney]

@sambg thanks for this post and you are 100% spot on the workflow now works.  Turn off the new interface before you do anything .  I hope we are not forced into using this until this is fixed

[LuisHermes]

The answer is you don't choose neither, you send your email inside the loop, that loop means for every time you receive a response you do this, in this case send an email.

[SharepointRex]

@JohnBunney 

@Tomijk 

Thanks for submitting - i have no answer, but I still have the same problem, and other coworkers.

We are using the flow to write 'new forms responses' to a sharepoint list.

This dumb foreach loop thing occurs because the new designer only has the option to 'get list of responses' under the 'Get reponse details' action. And so it uses the foreach loop because it gets the whole list of responses everytime someone submits a new response.

All we want is the 'New Response'.

The old designer did not have this 'get list of responses' in the action it only had 'Get response details'

It is a real pain switching between the 2 because the new is gr8 in many many ways.

I tried also using the Copilot - it puts a solution in, that doesn't cause the foreach loop, but it also doesn't fails because of a bad request.

Hopefully this is fixed not just left dodgy like so many poor quality issues prevalent in microsoft products.

[herschel4Iowa]

yep,. it was the new designer for me too, pulled my hair out for a few hours, followed steps on switching to old designer before adding any steps and it worked.