- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2019 09:36 PM
I'm attempting to run a simple comparison using the flow designer IF Flow Logic:
If [Date/Time 1] is after [Date/Time 2] then [do something].
However I receive an error on the flow with little to no detail on what the error is and the flow does not enter the if statement.
What would be the best way to debug the error? As the values appear to be correct. What would be causing this error?
Cheers,
- Mike
Solved! Go to Solution.
- Labels:
-
flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2019 08:41 PM
Update 1.1:
Confirmation received from HI/ServiceNow that this is a known bug with a fix in the 'Orlando' release.
In the interim a work-around such as the one in Update 1.0 can be used.
Or by changing the system wide date format to 'yyyy-mm-dd'.
Most Probable Cause: PRB1350626
Solution Proposed:
1. You are correct, this is a bug and has been fixed in the Orlando release as a part of PRB1350626.
2. Currently, it only works as expected when the date format in the system is set to yyyy-mm-dd
3. Anything other than this value will cause errors in a flow.
4. Hence, the workaround at this stage is setting the date format to yyyy-mm-dd.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2019 08:41 PM
Update 1.1:
Confirmation received from HI/ServiceNow that this is a known bug with a fix in the 'Orlando' release.
In the interim a work-around such as the one in Update 1.0 can be used.
Or by changing the system wide date format to 'yyyy-mm-dd'.
Most Probable Cause: PRB1350626
Solution Proposed:
1. You are correct, this is a bug and has been fixed in the Orlando release as a part of PRB1350626.
2. Currently, it only works as expected when the date format in the system is set to yyyy-mm-dd
3. Anything other than this value will cause errors in a flow.
4. Hence, the workaround at this stage is setting the date format to yyyy-mm-dd.