2
0
Commit Graph

9 Commits

Author SHA1 Message Date
BT-anieto
e3706c313d [FIX] account_move_name_sequence: call _inverse_name after computing the name
The core compute function for the name is calling at the end the function self._inverse_name(),
which updates the payment_reference when required.
This code was currently missing, causing the payment_reference not being properly computed,
for example, when using QR-Bills.
2023-10-18 07:52:25 +02:00
remi-filament
550df5a298 [FIX] account_move_name_sequence: computed fields raising warning 2023-03-15 11:45:31 +01:00
Rodrigo
18f890187a [FIX] account_move_name_sequence: With the "account_move_name_sequence" module the "_get_last_sequence" method does not have to propagate the with_prefix parameter. The sequence_prefix parameter will not be completed and will give error as it is False in this line of code. https://github.com/OCA/OCB/blob/16.0/addons/account/models/sequence_mixin.py#L169 2023-01-20 12:11:00 +01:00
Rodrigo
ab8e59d69d [FIX] account_move_name_sequence: call flush before _fetch_duplicate_supplier_reference method
same issue https://github.com/OCA/account-financial-tools/issues/1501
this fix not working for v16 https://github.com/OCA/account-financial-tools/pull/1514
2022-12-08 11:36:41 +01:00
Pierre Verkest
6599bfd112 [FIX] account_move_name_sequence: Use account move date to compute prefix
In case you want name your invoice YYYY-MM-SEQ (ie: 2022-07-00001)
where:
 * YYYY: is the account move year
 * MM: is the account move month
 * SEQ: is a numerical sequence that is continue along the fiscal year
   assuming fiscal year is over two years (ie: from july to june next year)

Before this commit the sequence prefix use now() to be compute but the
range is selected with the account move date.

This commit make consistency computing prefix with the account
move date as well.

So account move manage the first janunary for the last day of
the previous year will properly use the account move date.

Co-authored-by: Alexis de Lattre <alexis.delattre@akretion.com>
2022-11-22 14:36:51 +01:00
Francisco Javier Luna Vazquez
198724234a [FIX] account_move_name_sequence: Exclude no_gap sequences from _is_end_of_seq_chain 2022-11-22 14:36:51 +01:00
Moises Lopez
85cb94dc61 [REF] account_move_name_sequence: Moves with name '/' can not be posted
After remove required=True for journal.sequence_id field it is possible to post an invoice with misconfigured journal with empty sequence

So, this constraint will raise an error for this kind of cases since that using '/' could raise the unique constraint for all other moves
2022-11-22 14:36:51 +01:00
Alexis de Lattre
4aeaa9ca51 sequence is now required on journals
Add post-install script to create a sequence for all existing journals
Update README accordingly
2022-11-22 14:36:51 +01:00
Alexis de Lattre
42def7f06f Add module account_move_name_sequence
This module restores the good old behavior where journal entry numbers
were generated from a sequence configured on the journal.
2022-11-22 14:36:51 +01:00