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.
Service Portal: after manually entering a different date format from the user's date format, auto-correction will set the date to today's date - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Service Portal: after manually entering a different date format from the user's date format, auto-correction will set the date to today's date
KB0714166

Service Portal: after manually entering a different date format from the user's date format, auto-correction will set the date to today's date


424 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Build info: Jakarta patch 9b

Service Portal: after manually entering a different date format from the user's date format, auto-correction will set the date to today's date

Steps to Reproduce

1. Add variable type date to Apple iPad 3

2. Navigate to Applie iPad 3 on Service Portal.

3. Type into the date variable 18/8/8 and defocus (click somewhere else on the screen). The date is modified to appear as "2018-08-08".

4. Click Submit.

5. Navigate to the new REQ and then the contained RITM.

Expected bahavior: Date is shown as "2018-08-08"

Actual bahavior: Date is shown as "2018-08-06" (see the screenshot)


Workaround

After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided to not address this issue in any current or future releases. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem, contact ServiceNow Customer Support.

 


Related Problem: PRB1297443

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.