cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Advocate I
Advocate I

Boolean Inputs from User Change Case within Flow

Hello-

 

I am using the "For a selected item" trigger with a Yes/No input.  YesNo.PNG

Then I have the response emailed to me

True.PNG

I can see that the Boolean variable value is "True" rather than "yes".

 

Next I tried to use the variable value in a condition, but it failed.

Condition.PNG

Eventually I figured out that the variable needed to have a lower case "t".

Condition 2.PNG

So why is the Boolean varible "True" when I email it to myself, but "true" when I use it in a condition?  Why is it a an upper case "T" in one use, but a lower case "t" in the other use?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Support
Community Support

Re: Boolean Inputs from User Change Case within Flow

 

Hi @KA ,

 

Update reply from PG:

 

This is by design. In the condition, the property is used as its actual type (boolean), and when displayed in the run view is shown how booleans are represented, which is true/false. In the email it is being interpolated (formatted) into a string.

 

Here's another way of seeing the same thing. I've got a compose with the property, a compose with a leading space before the property, and a compose with the string the user was using.

 

The first one displays the boolean type "true". The second interpolates or formats into a string it with the leading space using the @{ } syntax. And the third matches what the user was using in their email, which is also string interpolation due to the @{ }

 

untitled.png

Please check it.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

6 REPLIES 6
Highlighted
Community Support
Community Support

Re: Boolean Inputs from User Change Case within Flow

 

Hi @KA ,

 

I am afraid this has caused confusion for you.

But for a long time, Boolean judgments use true/false to indicate Yes/No.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Advocate I
Advocate I

Re: Boolean Inputs from User Change Case within Flow

Hello-

 

I understand and acknowledge that Booleans are True/False rather than Yes/No.  What about my question: "So why is the Boolean varible "True" when I email it to myself, but "true" when I use it in a condition?  Why is it a an upper case "T" in one use, but a lower case "t" in the other use?"

Highlighted
Community Support
Community Support

Re: Boolean Inputs from User Change Case within Flow

 

Hi @KA ,

 

Thank you for your feedback. You could treat it as the actual value of Yes/No is true/false when used for logical judgment.

But when used as an output, the value will be True/False.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Advocate I
Advocate I

Re: Boolean Inputs from User Change Case within Flow

Hello-

 

So this really doesn't answer my question, which is: So why is the Boolean varible "True" when I email it to myself, but "true" when I use it in a condition?  Why is it a an upper case "T" in one use, but a lower case "t" in the other use?

 

It took many hours of troubleshooting my Flows to determine that that the first letter of the Boolean value changed case depending on where/how the Boolean value was used.  I have never seen this kind of behavior before in the 11+ languages I have learned.  Therefore I think it is a bug.

 

Would you please submit this issue to the Product Team as a bug?

Highlighted
Community Support
Community Support

Re: Boolean Inputs from User Change Case within Flow

 

Hi @KA ,

 

Pleasure, I would report this issue on my side. If there are any updates, I will post back.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Community Support
Community Support

Re: Boolean Inputs from User Change Case within Flow

 

Hi @KA ,

 

Update reply from PG:

 

This is by design. In the condition, the property is used as its actual type (boolean), and when displayed in the run view is shown how booleans are represented, which is true/false. In the email it is being interpolated (formatted) into a string.

 

Here's another way of seeing the same thing. I've got a compose with the property, a compose with a leading space before the property, and a compose with the string the user was using.

 

The first one displays the boolean type "true". The second interpolates or formats into a string it with the leading space using the @{ } syntax. And the third matches what the user was using in their email, which is also string interpolation due to the @{ }

 

untitled.png

Please check it.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Tech Marathon

Maratón de Soluciones de Negocio Microsoft

Una semana de contenido con +100 sesiones educativas, consultorios, +10 workshops Premium, Hackaton, EXPO, Networking Hall y mucho más!

Top Solution Authors
Users online (6,535)