The number counter is OOB, still - why does theerror comes up while inserting the service offering

mansigoel
Tera Contributor

The number counter is OOB, still - why does the error comes up while inserting the service offering : Invalid insert error thrown when a service_offering record is being created. Error : Check uniqueness for SN App Service ID <SN APP ID>". Business Rule stack:Check uniqueness for SN APP Service ID. 

 

Even when correcting it one time referring to this article : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0955143 , the issue occurred again. 

 

Does anyone know about this?

5 REPLIES 5

Rohit  Singh
Mega Sage

Hi @mansigoel ,

 

Are you sure that you have followed the below steps:

 

  1. please go to the table https://<instance_name>.service-now.com/cmdb_ci_service_list.do
  2. Add the Number column and sort (z to a)
  3. This will give you the last number on the table
  4. Now go to the Number Maintenance record of the prefix above
  5. Click Show Counter
  6. Update the Number to the last number on the cmdb_ci_service table

RohitSingh_0-1744023151052.png

 

RohitSingh_1-1744023211403.png

RohitSingh_2-1744023279694.png

RohitSingh_3-1744023344976.png

 

If my response helped, please hit the Thumb Icon and accept the solution so that it benefits future readers.

 

Regards,
Rohit

Hi @mansigoel ,

 

Are you sure that you have followed the above steps correctly.

 

If my response helped, please hit the Thumb Icon and accept the solution so that it benefits future readers.

 

Regards,
Rohit

 

Ankur Bawiskar
Tera Patron
Tera Patron

@mansigoel 

is that issue coming frequently or always?

how are you inserting? script or manually?

if you followed the steps from KB and still getting the error, please raise a case with ServiceNow.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hello Ankur,

 

We added it manually according to the KB, still facing this issue frequently.