What is the best way to avoid creating duplicate updateset name?

Kiran Kumar 76
Tera Expert

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

 

3 REPLIES 3

PrashantLearnIT
Giga Sage

Hi @Kiran Kumar 76 

 

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
********************************************************************************************************

Bert_c1
Kilo Patron

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.

Hitoshi Ozawa
Giga Sage
Giga Sage

I just append the date when the updateset was created with the name.