Case Switch - not using first 2 cases but always using default

[bryanc78]

I have a SP list that has a column that I use to document the request type and is using the multiple choice column type.

I have a flow created that looks to that column type and based on the answers, sends out an email.  However, it never uses my first two options and always defaults to the default option

If you look below, even though the item I created in SP has Sales in the Evaluation Type, instead of using that case, it uses the default case

ActionBranchingConditionNotSatisfied. The execution of template action 'Send_an_email_(V2)' skipped: the branching condition for this action is not satisfied.

Any ideas?

[Pstork1]

Can you show us the code you are using to initialize the variable?  and a recent run so we can see the value being assigned to the variable.  Normally some mismatch, like case or the wrong value, is the problem when a switch doesn't fire.

[bryanc78]

@Pstork1 

Here you go

[Pstork1 · Accepted solution]

I'm assuming that Evaluation Type is a column of type Choice.  If it is then the dynamic content you want is actually 'Evaluation Type Value' or something similar.  What you are actually storing in the string is a complex variable so you aren't getting the labels you expect.  Another way to verify that is to look at a recent run.  The Initialize Variable step should show you the value being stored.  It needs to match the case values exactly.

[bryanc78]

@Pstork1  Thank you!

[bryanc78]

@Pstork1 

One last question, if I add all of these to an existing flow, will it run them for everything in my list or just new items going forward?  I'm hoping since the flow is already created, it won't go back to ones from 2 months ago and send out new emails

[Pstork1]

It should only run for documents that are new or recently modified.  Older documents shouldn't be affected.