Edit Incident Management numbering scheme

[dvientos]

Hello Everyone,

I'm looking to integrate my instance of Service-Now with some of our vendors which are currently using Service-Now. The purpose is to move tickets back and forth and to enable my instance of SNOW to be the single source where everything is created.

One problem with integrating with another SNOW instance is that the other vendors have used the default Incident Management numbering convention (INC00001, etc)

If I use the default numbering scheme there is a chance there will be a mix up with my creating a INC00100 and an existing ticket in another system also being INC00100.

So is it possible for me to create a custom numbering scheme like, EINC00100 instead of INC00100? This would also apply for change and problem tickets.

Thanks,

Domenic

[andrew_venables]

Hi Domenic,

Numbering is controlled via Number Maintenance in ServiceNow and you can change the prefix to be anything you like, you can even change the start number to something much higher.

The whole topic is discussed at Managing Record Numbering - ServiceNow Wiki

Andy

[dvientos]

Thanks Andrew!

[adrian_collins]

Hello,

We are thinking of doing something similar for my client, but are concerned with the impact this will have on data and functionality already in the system.

Did you end up moving ahead with this change? If so, were there any issues you needed to overcome with historical data?

Thanks,

Adrian

[Deepak Ingale1]

Hello Domenic,

If you are integrating two servicenow instances, you should you the coalese mechanism for sys_id field.

That will ensure the unqueness and avoild mixup.