Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Valid_to date is set improperly when the date format for the system is changed to - dd-MMM-yy - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Valid_to date is set improperly when the date format for the system is changed to - dd-MMM-yy
KB0782953

Valid_to date is set improperly when the date format for the system is changed to - dd-MMM-yy


3030 Views Last updated : Jun 18, 2025 public Copy Permalink
KB Summary by Now Assist

Description

If the date format is set to YY year pattern (eg. dd-MMM-yy or dd-MM-yy) and user chooses a date either from the date picker or defaults the value for a date field from the server-side that is more than 20 years ahead of the current date, the saved record has a date that is 100 years older. For instance, if the user chooses 10-10-2050 and saves the record, the data that is saved will be 10-10-1950. This is true for default values set as part of the dictionary configuration as well.

This issue is more pronounced in Knowledge Management application as we have the valid_to field for new articles defaulted to 01-01-2100. If the date format uses a YY year representation, it leads to unexpected behavior of the valid_to date defaulting to 01-01-2000.

Steps to Reproduce

- Hop on to the New york instance (DemoNightlyNewyork).
- Go to system property - glide.sys.date_format
- Change the Date format to - dd-MMM-yy.
- Go to knowledge module and create a new article.
- Notice the Valid to Date is set to ==> 01-Jan-00 which is expired date.

Workaround

Do not use date formats that include only two digits for the year (eg. dd-MM-yy, dd-MMM-yy). Use a date format that uses 4 digits for the year (eg.YYYY-MM-dd,  MM-dd-YYYY).

Please note this is not a platform issue, two-digit year format shouldn't be used for representing a year. Please see the docs for more details:

https://docs.servicenow.com/csh?topicname=t_PersonalizeTheSystemDateFormat.html&version=latest


Related Problem: PRB1368628

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.