Comparing numbers in Flow Designer worked like comparing strings?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-04-2018 11:28 AM
Hi,
In Flow Designer I was testing an IF-statement where Expenses Record.Amount (type = Floating Point Number) value 25 should have been "<100". But unexpectedly the 25 was seen as higher than 100. When I changed the 100 into 300 it tested OK: the 25 was seen as less than 300. Which suggests the system thought that it was comparing strings. Any idea?
Kind Regards,
Annemie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2018 02:50 PM
Yes, indeed. 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-30-2018 11:58 AM
Hi Annemie,
I am having a different issue with flow designer conditions, but I'm wondering if there are similarities. Could you expand more on how the condition builder field was wrong?
I am trying to check if a field is blank, but there is not "is empty" operator. Instead, I have an action that returns a blank field and compares the value with this blank field. This works in some cases, but in others I keep getting the error {0}!={1} is not a valid conditional expression: null.
This may have nothing to do with your error, but i figured I'd ask 🙂
