Create Azure DevOps work item based on branched Microsoft Form section

[comorris]

Hello Team, I am trying to use Microsoft Forms branching capability to create work items based of the section completed by a user. This is being done in Logic Apps and the flow generally looks like this:

1. User navigates to Microsoft Form and answers the first question:

• Depending on the answer, the Form will branch to that path to fill out:

2) Once the user is under the next section, i.e. Process, they will fill out the form and submit.

3) At this point, depending on the section the user chose in the first question, I want to build a work item item in Azure DevOps. So, it will either be a work item for Process, Readiness, Automation, etc. 

How can I make logic apps branch off to create the proper work item template based off the Microsoft Forms section filled out?

I have tried using condition statements, but can't seem to get them to work! Any thoughts or ideas welcome and thanks in advance. 

[poweractivate · Accepted solution]

@comorris 

Rather than a Condition, try a Switch to branch between one of more than two options. 

Example:

Supposing a survey form like this:

Suppose the above Question with four options:

• Option 1
• Option 2
• Option 3
• Option 4

Also, supposing a single response with Id of 1 and a Response of Option 3 as below:

 Let's say you want to branch off for three possible branches -  Option 1, Option 2, and Option 3 (there could be more, but let's suppose three branches).

In this example, I get the Response with ID of 1 for my form (the only response there for this form in my example) with the "Get response details" Action:

Then right after that, I add a Switch.

In this Switch, I do as follows:

Under the "On" field I select "Question" from Dynamic Content so it will populate the actual response to the Question in there (in this example form, I had only one Question on there).

For "Case" I put Option 1 in the Equals Field.

Then I use a blue circle with a plus sign that appears on the upper right to add another Case

For "Case 2" I put Option 2 in the Equals field.

Then, adding another branch, for "Case 3" I put Option 3 in the Equals Field

For "Default" - which is the branch that runs if none of the Cases match - I leave nothing there, so that it will just "do nothing".

When I do a test run, I get the expected, desired behavior. One sign it is working is where it says "Expression result", it says "Option 3" which was the expected,desired value. What really shows that it is working though, is that Case 3 is the branch  that gets run, as indicated by the green checkmark shown below under "Compose 3" which is inside "Case 3". The grey "x" on the other branches means they were skipped - which is a good thing in this example and is what is the expected, desired outcome. 

You can adapt the above example as follows: Instead of Compose for each branch above, you can use the Azure DevOps related Power Automate Actions instead as needed to do something different based on which Case is run form the Switch.

See if it helps.

[comorris]

Thanks for the help! This is definitely what I needed.