Saturday, December 30, 2023
1 change · master
Miscellaneous changes
When we have more than one draft move for the same journal, it shows the gap sequence warning on the dashboard. Even if there is no gap sequence. It is caused by the fact that we used the sequence_prefix field on account move to check if a sequence exists. The aim of this commit is fixing the part of the sql query modified in 61c9bd69bb0342d845608ad0671e36c70f64fbd3 by verifying that the `name != '/'` like we did for the sql query that computes the made_sequence_hole field. task-3648745
Original PR description
When we have more than one draft move for the same journal, it shows the gap sequence warning on the dashboard. Even if there is no gap sequence. It is caused by the fact that we used the sequence_prefix field on account move to check if a sequence exists. The aim of this commit is fixing the part of the sql query modified in 61c9bd69bb0342d845608ad0671e36c70f64fbd3 by verifying that the `name != '/'` like we did for the sql query that computes the made_sequence_hole field. task-3648745 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#147006