- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2019 07:57 AM
Recently upgraded our Dev instance to New York and found an issue on an existing Date/Time variable in Service Catalog using the mobile app. Our default date format has always been set to MM-dd-yyyy. But when we select the Date/Time field and pick a date from the date picker, we get an Invalid date error. If I change our Default format to yyyy-MM-dd, it works fine.
This is only in the mobile app that we see this.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2019 05:27 AM
We actually stumbled onto either a fix or workaround, whatever you want to call it. While fipping glide.sys.date_format back and forth from MM-dd-yyyy to yyyy-MM-dd for testing, we inadvertently set it back as MM/dd/yyyy. It works fine now with the '/' instead of the '-'. ServiceNow support says it should work either way, but not for us.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2019 09:26 PM
You could always try change the configuration for the date time picker on the mobile app side if this is possible.
Other wise im not sure what else you can do other than raise a Hi ticket and potentially log a bug.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2019 05:27 AM
We actually stumbled onto either a fix or workaround, whatever you want to call it. While fipping glide.sys.date_format back and forth from MM-dd-yyyy to yyyy-MM-dd for testing, we inadvertently set it back as MM/dd/yyyy. It works fine now with the '/' instead of the '-'. ServiceNow support says it should work either way, but not for us.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2019 06:03 AM
I was just experiencing this issue today. I tried sgmartin's approach, but that didn't work at the time. I tried a few more fixes found in the forums, but none of those seemed to work either.
I then looked into my own profile settings and noticed that I had my 'Date format' field set to: 'MM-dd-yyyy'. I changed this on a whim to: '--none--' so that it'll take the system default time zone, which is set to 'MM/dd/yyy'.
I logged out of the mobile app and closed it. reopened it, logged back in, and it was working.
I do wonder if had I initially set my 'Date format' field in my profile to '--none--', would the above solution worked at that time, or the other solutions for that matter. Maybe.
At least this will give someone else another place to look before pulling their hair out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2019 02:39 PM
I have the same issues over here, and nothing worked for me so far. Shouldn't it be working with every date format?