- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2024 01:58 AM
Hi everyone,
I'm encountering an issue with my flow when using a decision table. Despite verifying all the input values being passed, the decision table consistently returns false during flow execution.
Has anyone experienced a similar issue or have any suggestions on what might be causing this? Any help or insights would be greatly appreciated!
Please see the below screenshot for more infomation.
my flow execution details said the input is India and the date is 2024-08-07 at 18:40:11
and here is the condition in that decision table. You can see the input value is matched and fell into one conditional statement/line and it should return True but the flow still returns False for this.
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2024 02:29 AM - edited 08-07-2024 02:29 AM
- Check the actual sys_id of the user location being passed against the sys_id of the location you have in the Decision condition. It is possible that you multiple location with the name India, and therefore there is no matching decision row. Look at the [sys_decision_question] table to see more details of your conditions including the encoded query.
- Try to change the table to [cmn_location] from [sys_user] on the DT input, and set the locations from that table directly.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2024 02:57 AM
The way I read your DT and the log, it seems that that DT uses a [sys_user] record as the reference with a dot walk to India.
However, in the LOG you feed the input as "India" while it should be a User Record that's the input and the DT will then dotwalk down to the location of the provided user and see if that matches the string.
So, check your inputs…
If helpful or correct, please state so!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2024 02:29 AM - edited 08-07-2024 02:29 AM
- Check the actual sys_id of the user location being passed against the sys_id of the location you have in the Decision condition. It is possible that you multiple location with the name India, and therefore there is no matching decision row. Look at the [sys_decision_question] table to see more details of your conditions including the encoded query.
- Try to change the table to [cmn_location] from [sys_user] on the DT input, and set the locations from that table directly.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2024 02:57 AM
The way I read your DT and the log, it seems that that DT uses a [sys_user] record as the reference with a dot walk to India.
However, in the LOG you feed the input as "India" while it should be a User Record that's the input and the DT will then dotwalk down to the location of the provided user and see if that matches the string.
So, check your inputs…
If helpful or correct, please state so!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2024 03:43 AM - edited 08-07-2024 03:45 AM
Thank you so much for helping me solve this issue!! @MattiasJonsson @Laszlo Balla
I am new to the decision table, and with both of your solutions, it made me understand how the decision table works more. Yes, both of you are correct. My input is India, which is the value from cmn_location, so once I change from the sys_user table to cmn_location, it works perfectly fine.
Thank you both again