Comparing two strings in flow designers always results to false
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2022 05:59 AM
For some reason in flow designer when comparing strings (even if they are equal) always evaluates to false. I tried trimming and changing the case to upper and lower as well, but nothing worked.
- Labels:
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2022 07:10 AM
Hi,
I faced same problem in my instance. It started working after I did the following: (Note - it is not logical but works)
1) Change condition to "is not" Executive -> Save the flow -> test the flow
2) Revert back the condition to "is" Executive -> Save the flow -> test the flow
Thank you,
Palani
Palani
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2022 05:12 AM
Unfortunately, I also don't have a solution but a similar problem:
In a Flow I want to compare a string Field against a String "DE" but if it has the same value, it always results in false.
It doesn't matter if I e.g., convert the letters of both strings in lower ones. I also rebuild the whole flow, but no difference.
The funny thing is that in other flows we already implemented the same method and it worked.
This is the field:
So, if anyone has an idea, I would be very grateful 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2022 02:03 AM
Hi,
I'm just wondering - can you copy an existing flow that works, and edit that? I know that the designer tends to remove data pills from the flow when you start changing things, but it's just a thought.
I have the same issue, and I tried reversing the logic to 'is not' (and saving) and then back to 'is', and it made no difference.
I'm going to keep looking for answers. I'll rewrite the action that outputs the string I'm trying to compare, to output a boolean instead.
Failing that, a Business rule might have to be written 😐
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2022 11:20 PM
The switch to 'is not' and back unfortunately also didn't help here.
We also worked around the problem and did it with a boolean instead^^'