importing case records in instance.

[Shruti Bhosale]

I am importing case record from other ServiceNow instance as that instance will be closed.

But when we are creating manually by clicking on new it is creating duplicate records with same number if system already have same number.

Please suggest.

[Robbie]

Hi @Shruti Bhosale,

For some context,  the unique identifier for all records, including duplicate records in ServiceNow, is the respective sys_id generated by the system.

By default, ServiceNow does not enforce uniqueness on the task.number column. This opens the possibility of having records with the same number.

The best way to resolve this issue is:
Ensure unique numbering on the table you're inserting into via a Business rule so that duplicate numbers will not be created. Before every update, it will make sure that a new number is assigned to the record.

Alternatively, enable a unique index on the table. Please Note: While unique indexes ensure data integrity they also prevent any insert involving a duplicate number. This may cause unexpected errors during data entry.

The business rule is probably the best option here.

To help others, please mark correct and helpful.

Thanks, Robbie

This is nicely detailed here but I've summarised it and provided context for you: https://www.servicenow.com/community/itsm-articles/duplicate-task-incident-numbers-being-generated/t....

[Robbie]

Hi @Shruti Bhosale,

Did you see my response below? Did it answer your question? To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Earlier response:

For some context,  the unique identifier for all records, including duplicate records in ServiceNow, is the respective sys_id generated by the system.

By default, ServiceNow does not enforce uniqueness on the task.number column. This opens the possibility of having records with the same number.

The best way to resolve this issue is:
Ensure unique numbering on the table you're inserting into via a Business rule so that duplicate numbers will not be created. Before every update, it will make sure that a new number is assigned to the record.

Alternatively, enable a unique index on the table. Please Note: While unique indexes ensure data integrity they also prevent any insert involving a duplicate number. This may cause unexpected errors during data entry.

The business rule is probably the best option here.

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Thanks, Robbie

This is nicely detailed here but I've summarised it and provided context for you: https://www.servicenow.com/community/itsm-articles/duplicate-task-incident-numbers-being-generated/t....