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.
History New Value [sys_history_line.new_value] truncated to 40 characters and does not Sys Audits New value [sys_audit.newvalue] - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • History New Value [sys_history_line.new_value] truncated to 40 characters and does not Sys Audits New value [sys_audit.newvalue]
KB0782007

History New Value [sys_history_line.new_value] truncated to 40 characters and does not Sys Audits New value [sys_audit.newvalue]


1777 Views Last updated : Sep 16, 2024 public Copy Permalink
KB Summary by Now Assist

Description

History New Value [sys_history_line.new_value] truncated to 40 characters and so does not Sys Audits New value [sys_audit.newvalue]. This prevents features like SLA History Walker from supporting GlideList field type as GlideList is a comma separated list of sys_id values. each sys_id is 32 chars long, so if more than one value is stored in a GlideList History New Value [sys_history_line.new_value] stores on valid sys_id, followed by one corrupted sys_id and no other values for the remaining records.

SLA Repair and SLA Timeline are both affected by this platform defect on GlideList.

Steps to Reproduce

1. In any form add more than one value to a list field, e.g. on incident form add two people to watch list field.
2. Compare History New Value [sys_history_line.new_value] to Sys Audits New value [sys_audit.newvalue]
Expected: History New Value [sys_history_line.new_value] to be identical to Sys Audits New value [sys_audit.newvalue]
Actual: History New Value [sys_history_line.new_value] is truncated to 40 chars

Workaround

1. Change the dictionary on History New Value [sys_history_line.new_value] from 40 chars to 4000 chars. Do the same for History New Value [sys_history_line.old_value]
2. Go to: Table Rotations. Select sys_history_line. Click UI Action: Synchronize Shards.

If the issue you are trying to resolve relates to SLA Repair and was caused by use of a platform GlideList field that was truncated then after completing the first two steps:

3. Run the following command in scripts - background on any record that has a task_sla with a broken SLA timeline. This rebuilds the history set and history lines for that incident.
new GlideHistorySet("incident", "<incident.sys_id>").refresh();
4. On the broken task_sla run UI Action: Repair.


Related Problem: PRB1349013

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.