Unneeded loops

[ay2]

Top part is inside an "if" condition while the other is outside. I don't understand why the first one would put the "get response details" inside a loop while the one outside doesn't... When it's in the loop, I can't extract that dynamic information outside of the loop. What I want is to take information in each of my branches and stick it all into a document, but with that loop I can't access the information in it... how can I get around this?

[Hardesh15]

@ay2 

Share your screen of Update Tracking for engineer. Is any column has multiple choice value?

Thanks

Hardesh

[ay2]

@Hardesh15 

The tracking does contain a bit of sensitive information, but the update is for an item in a SharePoint list. Once they put an assessment, it goes on a SharePoint list, AND ideally in a doc for archiving. It doesn't have a traditional multiple choice answer, but the form does contain a Yes/No option. I do not believe, however that it has anything to do with the loop. The "apply to" loop happened immediately after I added the "get response details", wasn't due to the update tracking step.

[Kikoger]

Hi,

I think there is something not quite right here. In your screenshot you have three triggers in parallel with an action above it and then some more towards the end of your Flow...? The "When a new response is submitted" is a trigger. There can only be one trigger per Flow. 

Apologies in advance if I am misinterpreting the screenshot - I'm just going my the labels.

Max

[ay2]

@Kikoger 

The one after the "if" statement is not required, just to point out my initial question. But you are correct, there are more than 1 "When a response is submitted" trigger in here. The thing is, this trigger works. While I'm annoyed the "get details" are put in a loop for seemingly no reason, it still does wait for forms to be submitted. If there are only supposed to be 1 trigger per flow, how would you suggest I work around this situation? 

My flow initially waits for a response to be submitted (A Forms response for a REQUEST). This gets sent for approval - and if approved, it sends off "x" number of assessments for this request ( this means "x" number of forms sent out). The step in the picture waits for all the assessment responses to be completed, then taking those answers into a doc before moving on with the rest of the flow.

[Kikoger]

Hi,

I'm afraid you cannot achive this with one Flow, as the trigger has to go at the top to function and is triggered when a form is submitted. At the same time, the action to evaluate the Form does not wait for a form to be completed after the trigger or something. It is an active action that simply get the response values for the form ID from the trigger.

If I understood right, you need the Flow to wait until certain Forms were submitted. In this case, you should record the form responses in an SP list and have Flow check the list periodically if the Forms were submitted according to your criteria and using loop exit flag in form of a Boolean variable. You can do that using the Do until loop and the built in delay function. It looks a little like the below. After each period of waiting, you need to get the responses you want to evaluate from SP and see if the condition upon which the Flow should snap out of the loop is true. If so, you should change the variable to true also. This will then cause the loop to end: 

I know this looks complicated, but basic rules apply here: One trigger per Flow - always at the top. Anything else will cause unexpected behaviour.

Max

[ay2]

@Kikoger 

Thanks for your quick response. This relates to another issue I had that was along the same lines. As far as I know, there is no "official" action to send a Form. My way was to use the "send an email" function and stick a link in that email for them to perform the assessment. In this step it waits for a person to perform an assessment. But how does the flow know if the "person I sent it to" completed that form, or if someone random person decided to just submit the same form for 0 reason? If this person completed it first, the flow would catch that response and use that instead of the person I actually wanted to do it