Yaltik/account-financial-tools
2
0
Fork 0
Code Pull Requests Activity

[FIX] account_journal_general_sequence: avoid renaming bottleneck

Browse Source 
When renumbering the moves, a lot of recomputes were executed, specially after Yeeeeaah was merged (a.k.a. https://github.com/odoo/odoo/pull/96134).

None of those recomputes is needed. The entry number we're adding here has no impact on taxes, invoices, or anything related. We can just skip all that stuff and make renumbering actually be able to finish in less than 100 years.

@moduon MT-2806
This commit is contained in:
Jairo Llopis 2023-04-24 10:09:27 +01:00
parent 2ce2187d9b
commit ea8bb553e2
No known key found for this signature in database
GPG Key ID: E47E3BE44B940490
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
account_journal_general_sequence/wizards/account_move_renumber_wizard.py
View File

@ -78,6 +78,7 @@ class AccountMoveRenumberWizard(models.TransientModel):
current_range.sudo().number_next = self.starting_number current_range.sudo().number_next = self.starting_number
self.sequence_id.sudo().number_next = self.starting_number self.sequence_id.sudo().number_next = self.starting_number
# Renumber the moves # Renumber the moves
moves = moves.with_context(skip_invoice_sync=True)
moves.entry_number = False moves.entry_number = False
moves.flush_recordset(["entry_number"]) moves.flush_recordset(["entry_number"])
moves._compute_entry_number() moves._compute_entry_number()