Overwriting auto generated number field - bad idea?

Viktor17
Tera Contributor

Hi everyone,

 

It's hard to find a good answer to this question, so I'll try the crowd intelligence here.


I have the requirement to import external data (excel sheet) to - let's say - the incident table.

The source data has its own number column (e.g. ABC-001234), while it's fairly close, it doesn't match with the automatically generated numbering from ServiceNow (e.g. INC00012345).

 

During the data transformation it would be an easy task to overwrite the number field with the "custom" one.

But I'm not sure whether this is a good practice or not.

The number from the source data needs to be in ServiceNow for sure. So you could simply create a custom field and store the information there, but I kind of don't like the solution, since there is a field for that which wouldn't really be used in this case.

 

Are there any business rules or other logics, which check for the "INC" prefix, or similiar and therefore the auto generated number should be used? Or am I missing something else?

Happy to hear from any experiences in this topic 🙂

2 REPLIES 2

Saloni Suthar
Mega Sage
Mega Sage

@Viktor17 You can use the Correlation ID (OOB) field to store the source number. 


If my response helped you, please click on "Accept as solution" and mark it as helpful.
- Saloni

Hey @Saloni Suthar,

that's a great idea, if the table is extended from the task table, like it is in my example.

But let's assume there is no "Correlation ID" field on the table. What would you do then?