Duplicated Invoice Numbers if 2 users generating invoices at same time

Well, i would agree that the numbers should be updated automatically, but we have discussed this internally, and there were other problems involved here. I will let Janusz comment on this.

Joe

Please list this feature on FA 2.4 release.

@itronics: An example of "separate identifier for every user" would be useful. Otherwise, all would have to wade thru the code for it. This may be explained in the Wiki. The following lists the possibilities.

Lines 55-66 in includes/references.inc:

$refline_placeholders = array(
    'MM' => 'date',
    'YY' => 'date',
    'YYYY' => 'date',
    'UU' => 'user',
     'P' => 'pos',
//     FIXME:  for placeholders below all the code should work, but as the ref length is variable,
//       length specification in placeholder format should be implemented.
//    'C' => 'customer',
//    'B' => 'branch',
//    'S' => 'supplier',
//    'L' => 'location'

Lines 302-332:

        $regex = preg_replace(
            array(
                '/\\\{/',    // unquote placeholders
                '/\\\}/',
                '/\{MM\}/',
                '/\{YY\}/',
                '/\{YYYY\}/',
                '/\{C\}/',
                '/\{B\}/',
                '/\{S\}/',
                '/\{L\}/',
                '/\{UU\}/',
                 '/\{P\}/',
                '/\{\d+}/',
            ),
            array(
                '{',
                '}',
                $month,
                $year2,
                $year4,
                $cust,
                $branch,
                $supp,
                $location,
                $user,
                 $pos,
                '\d+',
            ), $regex);

        $regex = '"^'.$regex.'"i';

Hi, please read post 4 above, which means you need to use {UU} in your transaction reference. So each ref will be unique.

The wiki entry is mentioned in post 7 above too, which also states to use this method.

Setup => Transaction References => Edit the "Pattern" field to include {UU} somewhere in it so that each user will have their own numbering.

Dear Apmuthu
So thanks
It works now
I appreciate your guide

At the beginning of Reference Pattern: you will see another box, you can add a preffix in there.
If you have already used the transaction ref, you may not be able to edit the prefix, so in this case make a new transaction reference

You may be able to useeither:-
1. {L} - Location, you will have to define each country as a location and sell from that location
Or
2.{P} - pos - Point Of Sale, each pos needs to be defined in setup against a location, which does come back to option 1.

In both casesyou will probably get just a number (of the location or pos), but you and your users will know what number each country is.

Please try on your training company first and report back for completeness.

Edit: I've had a quick look, it appears that pos can only be assigned to each user, which leaves just option 1.

???? Along side the {UU} add a {L} you can separate them with a '-' or a '/' if you want.

So some examples:-

{YY}/{MM}-{001} exactly as it is written with curly brackets and YY & MM. example gives 19/02-001

{YY}{MM}-{001} exactly as it is written with curly brackets gives 1902-001

{YYYY}/{MM}-{UU}/{L}-{001} exactly as it is written with curly brackets gives 2019/02-07/4-001 where 07 = user number and 4 = location number

{YY}/{MM}/{UU}/{L}/{A001} exactly as it is written with curly brackets gives 19/02/07/4/A001 where 07 = user number and 4 = location number

{YYYY}/{MM}-{UU}-{001} exactly as it is written with curly brackets gives 2019/02-07-001 where 07 = user number

{YY}/{MM}/{UU}/{A001} exactly as it is written with curly brackets gives 19/02/07/A001 where 07 = user number

You can add or remove placeholders as you want... as per this this wiki page see the code block following 'Supported special fields for each transaction type: '

Experiment on your trial company

When you sell an item you have an option to sell from a location which you can select, this is the location that will used in the ref #

You can read about locations here.

Read post 7 above:-

you need to uncomment:-

File:includes\references.inc
63: //    'C' => 'customer',
64: //    'B' => 'branch',
65: //    'S' => 'supplier',
66: //    'L' => 'location'

So that it reads as this:-

File:includes\references.inc
63:     'C' => 'customer',
64:     'B' => 'branch',
65:     'S' => 'supplier',
66:     'L' => 'location'

This is not currently implemented

Attempts to set reference {C} gives me the error
Invalid placeholder 'C'. Placeholders allowed for this transaction type are: MM,YY,YYYY,UU,P.