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.
Manual import of CI's and reconciliation/classification later by ServiceNow Discovery - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Manual import of CI's and reconciliation/classification later by ServiceNow Discovery
KB0718110

Manual import of CI's and reconciliation/classification later by ServiceNow Discovery


2259 Views Last updated : Jan 3, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Description


If you are manually planning to import CI's into ServiceNow, and planning to run Discovery on them later, you would need to import them into proper tables so that the Identification rules apply correctly and duplicates are avoided

Procedure


For example, when we insert a CI record into cmdb_ci table. We only give it a name field. When we run discovery, it creates a duplicate CI with the same name under cmdb_ci_computer.

Instead when we create a CI record on cmdb_ci_hardware table, after running discovery, the class of the existing CI changes from hardware to computer and there will be no duplicate.

Based on this, if you would like to do a manual import, it would be best to know what class the CI's might fall into. All the servers, network devices fall under cmdb_ci_hardware so you can import them under this table.

Regarding other CI's, you would need to make sure you know the class before importing. This will help prevent duplicates

Applicable Versions


All versions

 


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.