- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2024 11:37 AM - edited 05-02-2024 02:23 AM
I have few questions regarding sys_id.
1. Is sys_id unique per table or unique per instance or unique GLOBALLY across ALL the instances spinned up until now for all the customers world wide?
2. Suppose I create a user record, say its sys_id is "123". Later I will delete the record. Then can ServiceNow generate and use "123" again for new record?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2024 08:10 PM
In ServiceNow:
Uniqueness of sys_id:
- The sys_id is globally unique across all tables and instances of ServiceNow.
- Each record in a ServiceNow table is identified by a unique sys_id.
- This uniqueness is maintained globally across all instances of ServiceNow, regardless of the customer.
Recycling sys_id:
- Once a record with a specific sys_id, like "123", is deleted, ServiceNow will not reuse that sys_id for a new record.
- ServiceNow does not recycle sys_id values. Even if a record is deleted, its sys_id is not reused for new records.
- This ensures that historical references and relationships within the platform remain intact and consistent.
Please Mark ✅Correct if this solves your query and also mark 👍Helpful if you find my response worthy based on the impact.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2024 01:57 PM
Hi, a sys_id is a GUID and so is unique to the instance that it was created in.
Unique record identifier (sys_id) (servicenow.com)
As a unique identifier I would not expect a sys_id to be reused for a different record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2024 05:24 AM
So is it UNIQUE across ALL instances world wide?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2024 01:25 PM
A sys_id is unique and so if you generate one in an instance then it is expected that the same sys_id will not be generated by any other instance.
But, the same sys_id's can exists in multiple instances and normally these are default ServiceNow records or from store apps. Any customization you make that is moved to another instance (via update-set or clone) will also result in duplicate sys_id's, but these are always for the same record, with the same content (unless you customize to record).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2024 01:42 AM
Hi @Suggy
It depends,
if you are following the right way to move your data from Dev - Test - Prod then yes
but if you create instead of migrate ,same record 1st in dev and then in test then sys id will be different.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
