Switch" doesn't recognize one of the "Cases" and puts it in the "Defaut-Case" - Due to white space?

[EmmaHaraldsson]

Hi!

I have built a big flow with different "Switches". Now just one single switch doesn't work...

The whole flow works fine without errors, but what happens is that the "Switch" doesn't recognize one of the "Cases" and puts it in the "Defaut-Case" instead of intended case "Research & product development 2". This results in that no "Task" is created in any "Planner Bucket".

I think I found the error, but I cannot solve it... As you can see, there is a "blank space" after the Expression result "Research & product development".

I have checked the "Form" and the "Planner Bucket"- no "blank space" there. I have updated all inputs with new naming. I have created a new "Case" with the flow. Nothing works. Anyone who knows what to do about this?

And with raw inputs:

My whole flow looks like this:

The switch is set up like this:

Next "Switch" contains updating of "task details" depending on cases (I have not seen any errors in this yet) works fine for the other cases:

Please help ASAP!

Best regards

Emma

[Expiscornovus]

Hi @EmmaHaraldsson,

I see the answer ends with \t, which is a tab character. Have you tried removing that tab with an expression in your Switch action?

Try something like below: (change the question id to your question id)

replace(outputs('Get_response_details')?['body/r45eaa07074ac43cf9efb797fd51b091d'], '\t', '')

[EmmaHaraldsson]

Hi @Expiscornovus ! Thanks for your reply. I don't have a clue how to do as you suggested. Where do I perform such actions? I don't know anything about coding or programming, I'm just an "ordinary office-rat" that has started using Power automate to solve digitalization for some of my departments workflows... 🙄  

Try something like below: (change the question id to your question id)

replace(outputs('Get_response_details')?['body/r45eaa07074ac43cf9efb797fd51b091d'], '\t', '')

[Expiscornovus]

Hi @EmmaHaraldsson,

You can add this expression via the expression editor in the Switch action. Instead of the What type of request field.

Below is a small video/gif (click on it to see it in higher resolution/quality) to demonstrate what I mean

[EmmaHaraldsson]

Superthanks!!!

I did exactly as you showed...

But it still doesn't work 😥

Still ending up like this: 

Any other suggestion @Expiscornovus 

[EmmaHaraldsson]

It is only this type of "Request type" that acts like this. All the other 5 "Request types" works... all have the same "code".

Is it something in the form?

[Expiscornovus]

Hi @EmmaHaraldsson,

Yes, it is in the question of the form. You can also adjust the label in the question. That probably makes more sense.

Place the cursor at the end of your option. You should see some space between the t and the cursor. That is the tab character.

[EmmaHaraldsson]

@Expiscornovus  That, I have already checked, there is no "tab" there... 😞 

Any other ideas?

[EmmaHaraldsson · Accepted solution]

I finally solved this myself. Still don't know what caused the problem. 

The solution was:

1. Remove the option (that caused error) in the form. 
2. Add a new option in the form.

Sad that I didn't think about this in the beginning.... But now it works, and that is what counts. Thanks @Expiscornovus  for your efforts trying to help me! Really appreciated!

[Expiscornovus]

Hi @EmmaHaraldsson,

About the root cause. I am pretty sure there was a tab character in your answer, it is actually shown in one of your screenshots with the Expression results (It is the ->, not very noticeable, but it is there)

2. You can actually see that same type of characters if you Show the paragraph marks and other hidden symbols in Word and use a tab at the end of your answer

[EmmaHaraldsson]

@Expiscornovus Yes, that is definitely the root cause, this I spotted from the beginning, but where it comes from... and how to get rid of it (except for my solution), that I cannot understand.

The replacement you suggested, didn't work, and there were no space in the form. 🙄

I think it must be some kind of bug, as I put it exactly the same same way when I created the new option.