Date variables showing wrong

kristenankeny · ‎11-17-2016

We have a situation with date variables, but have not yet figured out how to reproduce the issue. Occasionally, users will submit requests for items that have date variables. At some point in the process, the date will display an odd value. Users sometimes try correcting the date, which then shows that the original value was the right date value, but again new value is odd.

Here is an example of a variable's history:

Does anyone have any experience with this and any suggestions as to what might be happening? We aren't scripting anything with the date variables after the requested item is created.

kristenankeny · ‎01-12-2017

After talking with ServiceNow, it sounds like there is a known bug that is difficult to replicate, but is caused by to overlapping items:

OOB methods for date variables does not properly handle situations where a user has selected a personal date format that is different from the system format (this is especially true with date formats beginning with dd)
The variable pool seems to be shared and another user's selected date might be stored, causing the date the current user is attempting to enter to be corrupted

Our current solution for this, though we are not positive it will resolve all issues, given that there might be a problem with regard to the variables, is to remove the ability for users to select personal date and time formats and to only use the system date and time formats.

View solution in original post

Kalaiarasan Pus · ‎11-17-2016

Take a look at this thread

Date being converted to an invalid date automatically by system

kristenankeny · ‎11-17-2016

Thanks for the suggestion. I took a look and I'm not sure that's talking about the same issue. The frustrating thing is that it isn't always wrong and I can't seem to be able to reproduce it, even using the same set up and users and the ticket that had issues.

chris_deegan · ‎12-15-2016

Hi Kristen,

Did you have any luck figuring this out, I am having the same issue as you? In fact the year that it is inputting incorrectly is the same year that you have in your screenshot.

kristenankeny · ‎12-15-2016

Hi Chris,

Not yet. I found I could replicate the issue if I set my personal date format to one starting with dd, if we were using a script to populate the field and weren't using the set by format. When you push setByFormat using the user's format and they have one of the formats starting with dd, then the script fails completely after populating one date field with the date value in the right format for the current user. We have a ticket in with HI about the dates showing incorrectly (which we're seeing on fields where we don't set the value through script as well), and they've been slow about getting back to us and finding the source of the problem. I sent them another update today with the additional issues we're seeing. If a resolution is found, i'll update this.