Search options (Page 1 of 2)

For Bank Account Transfers, the solution is similar to the others: we update the ref before the check_reference() runs. The file to edit is gl/bank_transfer.php

    /////////////// update ref 
    $_POST['ref'] = $Refs->get_next(ST_BANKTRANSFER, null, $_POST['DatePaid']);
    if (!check_reference($_POST['ref'], ST_BANKTRANSFER, $trans_no)) {
        set_focus('ref');
        return false;
    }

Just got a solution for customer payment.

In the can_process() function in sales/customer_payments.php, I update $_POST['ref'] with the next available ref before check_reference() runs. That means, if the ref on the form is used, the next available will be chosen and the problem of used ref will never occur again.

I'm particularly happy that no warning message is displayed on the form to the user. That's exactly how I wanted it.

The code is as below:

    ////////// setting  $_POST['ref'] to the next available ref
    $_POST['ref'] = $Refs->get_next(ST_CUSTPAYMENT, null, array('customer' => get_post('customer_id'), 'date' => get_post('DateBanked')));
    if (!check_reference($_POST['ref'], ST_CUSTPAYMENT, @$_POST['trans_no'])) {
        set_focus('ref');
        return false;
    }

Just installed it - FA 2.4.3 - but  the same problem. Sales order is OK but not customer payments, bank payments, bank transfers, location transfers, inventory adjustments.

In our case, there are different users entering data at the same time. If two or more open the same form, they'll be assigned the same ref. After one saves successfully, the others will encounter The entered reference is already in use..

That is when references need to be changed.

Changing it manually was also not the best for us since instead of manually changing from say 134/2017 to 135/2017, sometimes they'd type funny things like 1352017 or 1355/2017 or 135/2o17.

If it's automatic, none of these problems.

Oh yes, you're right. It works like magic. Just had to comment out those two other lines as below:

unset($_POST['ref']); // force refresh reference
display_error(_("The reference number field has been increased. Please save the document again."));
//$_POST['ref'] = $_SESSION['Items']->reference = $ref;
//$Ajax->activate('ref');

Thank you, thank you, thank you all

Yes, I think that'll be great.

In the interim though, any way I can get the value in the ref field on the form increasing to the next available ref? Or automatically saving with the next available ref if the one displayed is used?

No sir, it notifies the user but does not update/increase the value of the ref field on the form to the next available ref.

So I want achieve one of two things:

1. Either the user is notified that the ref is used and the ref field on the form is changed to the next available field

2. Or the user is NOT notified that the ref is used but when saving, it automatically discards the used ref and uses the next available ref

OK, what if I want to use the next available ref to save without prompting the user if the one on the form is already used?

For instance, let's say the ref on the form is 155/2017 but it's already used. Instead of prompting the user that it's used, I want it to automatically pick the next available, say 157/2017 (assuming 156/2017 is also used) and not prompt the user but rather just go ahead and save the order with 157/2017.

How do I do that? How do I skip the prompting and just go on to save with the next available ref?

The display_error($_POST['ref']); displays the next available ref but the ref field on the form still has the old, used ref