REQ increment by one

[VL10]

Across our instance, so from main app or via a service catalog. the generated REQ always skip one.   Is this a config setting or intentional mandatory behavior?

[Mark Roethof]

Hi there,

Can you explain a bit more what you mean with always skip one? Skip what exactly?

[VL10]

REQ numbers skip one, so we create REQ0081708 then REQ0081710 then REQ00817012.   This occurs for all REQ generated from ServiceCenter catalog items.

[Mark Roethof]

It's not "intentional mandatory behavior" like what you mentioned in your question. Out-of-the-box this works fine.

Did you try to reproduce the steps on a PDI, so you can compare it yourself?

[Community Alums]

If you go to the data dictionary for number in the Request table, there is a field called dynamic default value which calls javascript getNextObjNumberPadded. You can investigate this script to see how the autonumbering is working out of box