Invalid Date error after running a 'Check Conflicts' on a change request for a user who has date format set to anything other than system format - Known Error

Invalid Date error after running a 'Check Conflicts' on a change request for a user who has date format set to anything other than system format Description Saving a change request after running a check conflicts causes error Invalid date on Conflict last run field. This happens for a user for who the date format is set to anything other than system date format.

Steps to Reproduce

On a Jakarta OOB instance version glide-jakarta-05-03-2017__patch0-05-18-2017

Set current user profile Date Format to anything other than system format. For example, as an ITIL user set the date format as dd-mm-yyyy On a Change Request, set Planned Dates that generate a conflict, then Save record. This works correctly as expected. After reload, navigate to Conflicts tab, and click on Check Conflicts This changes the field Conflicts last run date time value. Save the change record. Result: Invalid date error appears under Conflicts last run date time field.

Workaround This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.