What is the best way to avoid creating duplicate updateset name?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2024 09:01 AM
Avoid duplicating of updateset name while creating new updatesets
Tried unique dictionary but it gives me duplicates already exists error and not saving
How can we handle default updateset which will be created with all scopes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2024 09:23 AM
The Default update set should remain as it is as simple to follow this best practice.
Please appreciate the efforts of community contributors by marking the appropriate response as the correct answer and helpful. This may help other community users to follow the correct solution in the future.
********************************************************************************************************
Cheers,
Prashant Kumar
ServiceNow Technical Architect
Community Profile LinkedIn YouTube Medium TopMate
********************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2024 09:49 AM - edited 10-27-2024 01:24 PM
And for the first question, sort or group the list of sys_update_set table records by name. Or create a business rule on that table, that checks the 'name' and 'application' for an existing record with the two field values. You can also use a client script and script include to enforce uniqueness.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2024 04:24 PM
I just append the date when the updateset was created with the name.