-
-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MIG] account_move_name_sequence: Migration to 15.0 #1409
Conversation
This module restores the good old behavior where journal entry numbers were generated from a sequence configured on the journal.
Add post-install script to create a sequence for all existing journals Update README accordingly
…ge lines data based on current moves
…ange_day More info about: - odoo/odoo#91019 TODO: Revert this commit after it is merged
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
The required flag was wrong for sequence_id and refund_sequence_id So, it was not possible to store any change in journal for journal different to sale and purchase
Hi @moylop260 I made the migration of the module, can you review it? cc: @luisg123v Note: Red on tests with odo + OCB not related to account_move_name_sequence module |
I think the red on tests are related with this module For v14.0 the So, the following commit was required: It was thanks to Sbidoul help from comment: For v15.0 I see Could you check if it is rebel or if the unittests needs to be changed, please? |
@frahikLV, Be careful with te branches used. You're merging 15.0 from vauxoo-dev into 15.0 of OCA |
Superseded by #1410 |
No description provided.