- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2016 07:43 PM
Hello Community,
I was wondering if anyone on here would know why this situation would occur. It seems that a user has created two Change Requests.
The odd part is they both have the same UID and I thought that ServiceNow would never created the same UID for any record.
Could this be cookie related? I would have a similar issue with workflows and was wondering if this was the same type of situation.
I have provided screen shots below. If there are any fixes please let me know as I am all ears.
Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2016 08:57 PM
I have seen similar behavior when user clicked the update/save button twice to create a change record. But this looks like 3 hrs apart. There is a lot of talk about duplicate numbers in the community and wiki there is a problem record also for this.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2016 08:28 PM
Hi Orlando,
While it should usually get the next number in sequence, this is not the unique id. The sys_id field is the unique identifier for each record, but what you're referencing is the number field. It's possible to enter non-unique numbers in this field... if a user has access to change it, or possibly if you have a script functioning improperly somewhere.
Thanks,
-Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2016 08:57 PM
I have seen similar behavior when user clicked the update/save button twice to create a change record. But this looks like 3 hrs apart. There is a lot of talk about duplicate numbers in the community and wiki there is a problem record also for this.