auto upgrade numers(number maintenance) storage

[vits18735a0]

Auto upgrade number (number maintenance)  i incident,problem,change request and any cutome tables which have the auto update number.  Than every time we open the record ,so it creates new number and with out saving that record we reload than the auto update number is again update to next padding number. so in real seanarios all the number's which are not saved are junk? 

in many times we can open the incident form to modify and verify the new updates and design so than, we did not want to lose that generated record right? or we can just ignore those record numbers? 

is it possible to restrict the incident table auto update numbers like one previous records saves( INC0001 saves ) than only another record( INC0002) number will generate. if we reoad the form the same INC number will present there untill we save the record?

[Maik Skoddow]

Hi @vits18735a0 

Set the property glide.itil.assign.number.on.insert to true. This property ensures that the number is assigned only upon record insertion (save), not when the form is loaded.

Maik

[Asha J]

there is a property for it

[anubhavbans]

Are These Junk Numbers a Problem?

• Technically, no — most systems treat these as non-critical gaps.
• But for auditing, reporting, or compliance, it can be confusing to see missing numbers.
• In production environments, this can be seen as wasteful or misleading.

[Chaitanya ILCR]

Hi @vits18735a0 ,

set the property to true

glide.itil.assign.number.on.insert

 setting it to true make sure the number will be generated after the record is inserted into the record

you see my responses on below thread

https://www.servicenow.com/community/workflow-data-fabric-forum/when-creating-an-incident/m-p/328842...

Please mark my answer as helpful/correct if it resolves your query.

Regards,
Chaitanya