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.
Resolving Date/Time Display Discrepancies in Web Services - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Resolving Date/Time Display Discrepancies in Web Services
KB0546240

Resolving Date/Time Display Discrepancies in Web Services


7788 Views Last updated : Apr 30, 2024 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

Date and time values have both a value and a display value. Inconsistencies between these values can lead to unexpected behaviour. The value is the raw value within the database. The display value represents the user-friendly value shown in the UI. Certain field types such as Encrypted text, DateTime, choice, and reference fields all also use a display value that differs from the raw value.

With DateTime fields, the raw value is always stored in the UTC timezone, while the display value appears in the timezone set for the current user record.

Symptoms

  • Date and time values appear different than expected
  • Entering a date and time value using web services results in a different value appearing in the UI

Cause

By default, web services use either the display value or the raw value depending on the operation.

  • SOAP Insert or Update operations treat request values as display values
  • SOAP retrieval operations return raw values
  • JSON operations all use raw values
  • REST Table API retrieval operations return raw values
  • REST Table API Insert or Update operations use display values for certain fields (you can force the REST API to always use a particular type of value using the 'sysparm_input_display_value' parameter

Resolution

You can explicitly specify the format you want the operation to use by adding a parameter to the request URI.

  1. SOAP and JSONv2: add the display value parameter. Valid values are true, false, and all. For example, to use only the display values:
    <instance>.service-now.com/incident.do?SOAP&displayvalue=all

  2. REST retrieval operations: add the sysparm_display_value parameter for retrieval operationsValid values are true, false, and all. For example, to return only the display values:
    <instance>.service-now.com/api/now/table/incident?sysparm_display_value=true

  3. REST Insert or Update operations: add the sysparm_input_display_value parameter for Insert or Update operations. Valid values are true and false. For example, to insert data using only raw values:
    <instance>.service-now.com/api/now/table/incident?sysparm_input_display_value=false

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.