Answered

Flow trigger condition not working

(2) Share

Report

Posted on by Frac

200

@And(equals(triggerBody()?['ApplicationWithdrawn'],false),not(equals(triggerBody()?['ManagerNomination'], triggerBody()?['NominationType'])))

This is my trigger condition that is supposed to only let my flow run if applicaton withdraw is false, and if Mnager nomination does not equal nomination type.

Nomination type is a text field, and manager nomination is a multiselect field, i think this is the reason it is now working, but i am not sure what the correct syntax is in this situation.

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Suggested answer

Pstork1 69,547 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Since Manager Nomination is a multiselect field you can't really use equals. Instead you should use the contains operator. It should be something like this

@And(equals(triggerBody()?['ApplicationWithdrawn'],false),not(Contains(triggerBody()?['ManagerNomination'], 'triggerBody()?['NominationType']')))

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Suggested answer

11manish 3,122 on at

Like
a
(1)

Report
Copy link

Link copied!

The issue occurs because you are comparing a multi-select field (array) with a text field (string). Instead of using equals,

you should use contains to check whether the text value exists within the multi-select array, and wrap it with not() for your condition.

If the multi-select field is stored as an object array, you may need to use join() to convert it into a string before applying contains.

Was this reply helpful? Yes No
Verified answer

Valantis 6,569 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Frac,

Both are answers above are correct on the approach. Just to add the clean corrected syntax since the expression above might have a quoting issue:

@and(equals(triggerBody()?['ApplicationWithdrawn'], false), not(contains(triggerBody()?['ManagerNomination'], triggerBody()?['NominationType'])))

If your multiselect field returns an array of objects rather than an array of strings (common with SharePoint choice columns), contains won't find a plain string match. In that case use join first:
@and(equals(triggerBody()?['ApplicationWithdrawn'], false), not(contains(join(triggerBody()?['ManagerNomination'], ','), triggerBody()?['NominationType'])))

If it's still not working after that, add a Compose action in the flow body to output triggerBody()?['ManagerNomination'] and run it once so you can see the exact format the field returns. That will confirm which version of the expression to use.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Valantis 6,569 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Frac,

Just wanted to check in and see if everything is working now. If you still need any help, feel free to let me know.

Also, if the issue is resolved, it would be great if you could mark the answer as solved so others with the same question can find it easily.

Thanks and have a great day!

Was this reply helpful? Yes No
Suggested answer

Haque 3,557 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @Frac,

Your guess is correct - already solution is discussed. I would just add one thing - before giving a complete conditaion a try, can you please narrow down the check first with contains(triggerBody()?['ManagerNomination'], triggerBody()?['NominationType']) to make sure it works? Then use the complete condtion that Valantis mentioned.

Was this reply helpful? Yes No