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.
Duplicate Service Desk record numbers being created - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Duplicate Service Desk record numbers being created
KB0693925

Duplicate Service Desk record numbers being created


1483 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


Duplicate records (same 'Number' value) in the Service Desk [new_call] table. This can be reproduced using these steps:

  1. Log into an instance
  2. Ensure the plugin 'Service Desk Call' has been activated.
  3. Go to new_call.list
  4. Create a new record then 'Save', make a note of the number.
  5. Go to new_call.list
  6. In the breadcrumbs filter, search for 'Number' is '<NUMBER>' // Number from STEP 4
  7. Click on 'New'

Release


All

Cause


This behavior is by design. More information can be found in the doc titled Filters and breadcrumbs

"Clicking the New button in a filtered list automatically applies the same filter to the new record. For example, clicking New in the Resolved Incidents list opens a record preset with State set to Resolved. In a list filtered for active, priority 1 incidents, clicking New opens a record preset with Active selected and Priorityset to 1 - Critical.

You can change the preset values on the form as needed. If there is a field you do not want to have populated in this way, you can add the following dictionary attribute to the field: ignore_filter_on_new=true."

Resolution


If there is a field you do not want to have populated in this way, you can add the following dictionary attribute to the field: ignore_filter_on_new=true.

 


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.