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.
Record number prefix is not working properly / Case numbering issue - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Record number prefix is not working properly / Case numbering issue
KB0854384

Record number prefix is not working properly / Case numbering issue


1392 Views Last updated : Jul 25, 2023 public Copy Permalink
KB Summary by Now Assist

Issue

This issue can be seen when the number prefix is not followed like it is supposed to.

Here is an example:

TASK0001001 <-- As seen here, this number has the 'TASK' prefix and followed by 7 numbers.

Maybe the number on your record after it generates is only 1001, or 0001001 without the 'TASK' (Or any) prefix.

Cause

This could usually be caused by 1 of 2 things.


1. The prefix record does not exist on the 'sys_number' table.

2. The prefix record exists, but is being overridden on the 'sys_number_counter' table.


If the prefix record exists on the 'sys_number' table, often times the issue would lie in the 'sys_number_counter' table.

Imagine the table that is having this issue is "sn_hr_core_case_workforce_admin". Whenever a record is created on this table it just shows 1001 and increments by 1 per every record created.


The 'sys_number' prefix exists for the 'sn_hr_core' table which carries down to the 'sn_hr_core_case_workforce_admin' table.

The issue was found in the 'sys_number_counter' table, as this number counter system was being overridden by a customer created number counter record.

The record was added on 'sys_number_counter' for the table 'sn_hr_core_case_workforce_admin', and with the number 1000 attached to it.

This overrides the parent 'sys_number_counter' record and now stops the prefix from showing.

Resolution

In the above case where 'sn_hr_core_case_workforce_admin' wasn't showing the proper prefix, the issue was lying within the 'sys_number_counter' table.

A user created a record on that table that overrode the parent 'sn_hr_core' record.

The fix was to remove this record so that the parent prefix and number system would take back over.


If you are experiencing these issues, please check both the 'sys_number' and 'sys_number_counter' tables. Verify that these records are attached to the proper tables with the proper Prefix.

Also keep an eye out for parent tables that create the prefixes and what number is being assigned to the records.


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.