To me it's wrong having a preference setting asking for a prefix and a number. Because when you jump from say, 9 or 99... to 10 or 100.. the total number increases by 1. So, in my case, the prefix is set to 00000. But when i reach the number 10 it goes like this:

000009 => 0000010

That's wrong. It should go like this instead:

000009 => 000010

That is, the prefix automatically shortens by one if the number increases by one.

Can it be fixed soon, please?
By now I'll modify it manually.

Bump!

Anyone from Marketcircle cares about?!?

Don't have a fix for this yet, but it is in our system.

Andrea,

This does work, the issue here is where you are specifying the padding.

The Prefix field is used to specify an alphanumeric prefix which can be dynamically generated through tokens. It does not contain the padding of the number.

The Number field is the field which contains the next number to be used and it should include the padding. Once a number increments beyond the ones digit lets say, it will take over the padding found in the 10's digit, as you are specifying.

So... an example for an invoice is..

Prefix = ABC-INV-
Number = 000009

The next invoice to be generated will have the invoice# - ABC-INV-000009
The invoice after this invoice will have the invoice# - ABC-INV-000010

The padding needs to be specified in the Number field along with the next number to be used.

This is specified in our help documentation under "Setting up estimate and invoice numbering"

It states...

For example, you can set your first estimate to be numbered 1 or 001 or 0001. If this is the case, Billings numbers your second estimates as 2 or 002 or 0002 respectively. Billings 2 respects the 0 padding specified in the number field.

"Billings 2 respects the 0 padding specified in the number field. " -- this is the important line, which could be clearer by providing an example. We will resolve this documentation issue in a future version.