No Series Extension

navtest

Running out of Number Series soon.
We have String+Number as the design
What would be the technical impact if I change the number Series from PO9999 to PO99999 and I needed to add one more 0 to the last number used as PO09837 from PO9837
I am concerned because of
1. Sorting
2. Impact in custom Dataports
3. code units
4. Historical data

Any suggestions? BDTD?

vaprog

Sorting is alphanumeric (at least on SQL, not sure about native, but you have to think ahead to SQL anyway), so your proposed change breaks chronological sorting.

What kind of difficulties do you expect on the other areas you named?

With numbers at PO9837 already, you could change to PO990000, but those two '9' would need to stay. If you reached PO99xx already, one more digit will be partly lost.

Rather use a different character prefix such as PP or PQ and maybe then also more digits. You can then decide according to your liking whether you want to start that sequence at 1 or the last number of the PO series +1.
You may also just use letters for the left most digit on carry, ie. PO9999, POA000, POA001 ... POA999, POB000 ... and probably best add some more digits at the end (the same principle as with Hex numbers, but not limited to letters A to F) ie. PO9999, POA000000.

With increased lengt of the number you need to check document and report printouts, and in fixed length data exchange formats the field widths.

In C/AL code you should have used variables and fields of type Code 20 anyway.

Marije_Brummel

NAV Automatically adds a digit to the number.

If your last number is S99 the next will be S100