We’ve been using NetSuite for about 6 months now a...
# generale
eblackey
12/15/2021, 2:05 PMWe’ve been using NetSuite for about 6 months now and have about 1.3M transactions. But, I noticed that our current transaction id (internalid) is already up to over 10M. Is that normal? Why does NS skip so many numbers on the internalid? Is it to prevent race conditions or something like that?
k
karlenigma
12/15/2021, 2:35 PMthe internalid is for all transactions. Journals, Invoices, Sales Orders etc etc
karlenigma
12/15/2021, 2:36 PMalso if some get deleted it doesnt re use an already used id it just continues from the last one.
👍 1
n
NElliott
12/15/2021, 5:07 PMAlso if you run a map/reduce that creates records you will find it jumps numbers too for the reason you mentioned @eblackey
👍 1
e
eblackey
12/15/2021, 7:35 PMOh interesting. That’s probably what’s going on.
eblackey
12/15/2021, 7:36 PM@NElliott Do you know if there’s any documentation on that or did you just learn that through trial & error?
k
KevinJ of Kansas
12/15/2021, 8:01 PMIf you are using internal ID for anything other than pointing things at the right record you are abusing the concept
e
eblackey
12/15/2021, 8:53 PM@KevinJ of Kansas Yeah, understood. We’re not using it for anything special. The reason I was a little concerned is that our old ERP system had a limit on the transaction ID “auto number” field and we were only a couple of years away from hitting that before we moved to NetSuite. I seriously doubt that’s a problem or we wouldn’t be the first to see it. But, just wanted to learn more about it.
k
KevinJ of Kansas
12/16/2021, 1:00 AMI wouldn't have any stress over that one.
n
NElliott
12/16/2021, 9:22 AM@eblackey This has been talked about in Slack before, quite recently actually, it wasn't something I observed or have seen documentation about. As I recall the numbers were jumping 100 at a time on a Map/Reduce as observed by others.
Also, I'm sure autonumbering doesn't stay aligned with the internalid. I you will see #SO100 and the internalid could be 123, one is not a reflection of the other, so the internalid jumping is not something that should be of concern to you from a transaction numbering perspective. (unless you've relied on some correlation in the past, eep!)