Avoid writing multiple variables using Parse JSON (or any other action)

[pedrosf]

Hello, I'm currently building a flow with teams' approval.

Depending on a sharepoint list value, the approvers will be different.

For example, if the departments concerned are football and fitness, the approval will be sent to each chief.

Instead of setting new variables, I'd like to know how to put together the if expressions.

if(contains(body('Get_items')?['Department'],'Football'), 'footballboss@@.com', '')

if(contains(body('Get_items')?['Department'],'Basketball'), 'basketballboss@@.com', '')

if(contains(body('Get_items')?['Department'],'Handball'), 'handballboss@@.com', '')

if(contains(body('Get_items')?['Department'],'Hockey'), 'hockeyboss@@.com', '')

if(contains(body('Get_items')?['Department'],'Fitness'), 'fitnessboss@@.com', '')

if(contains(body('Get_items')?['Department'],'Others'), 'othersboss@@.com', '')

Still thinking how to get the true values from Parse JSON

Finally getting the compose to "Assigned to field"

[abm]

Hi @pedrosf 

I am not sure about the JSON If statements you mentioned. You could do this via switch action step.

Declare a string variable called email. Then retrieve the items using Get Items. Add a switch action step to determine the category and store the email under the new variable. Finally send email using the variable which will have the email address.

Thanks

[pedrosf]

Hello @abm, 

Thank you for answering my request.

I've already flow with a switch setup but I dont'know if the cases "Equals" field triggers if the sharepoint values are written like this.

[abm]

Hi @pedrosf 

Here it is

Above the Parse JSON is as follows:

{

    "type": "array",

    "items": {

        "type": "string"

    }

}

Thanks

[pedrosf]

Hello, 

I tried for the last 3 hours to get this through but the "Equal" field doesn't detect the words in the "Expression result". 

It always goes to default.

(To get the "Outputs" in Parse JSON content filed, I had to put the dynamic content in Compose after)

[abm]

Hi @pedrosf 

I am pretty sure you are mapping the wrong mapping in your switch

See my mapping

[pedrosf]

Hello,

That screenshot you mentioned is the result of the flow.

I have the same thing as you.

[abm]

Hi @pedrosf 

Thanks for the screen share. All we did is rearranged the flow similar like my earlier screenshot.

1. Extract the values from SharePoint

2. Parse JSON

3. Iterate each values

4. Switch 

Thanks

[pedrosf · Accepted solution]

Hey,

Here is the final flow.

Don't forget to use the Parse JSON "Generate from sample" with your compose output.

Thank you so much @abm.