-
-
Notifications
You must be signed in to change notification settings - Fork 308
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
[16.0][FIX] l10n_it_delivery_note: create delivery note only after quantity done has been set #4526
[16.0][FIX] l10n_it_delivery_note: create delivery note only after quantity done has been set #4526
Conversation
Hi @MarcoCalcagni, @renda-dev, @aleuffre, |
be8bd99
to
d3b9b6f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
functional review ok
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grazie 1K della PR! Review del codice 👍
Solo giusto un paio di nitpick:
- aggiunta di un commento alla parte di codice modificata
- modificare il commit message come indicato su https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#commit-message
The method stock_picking.button_validate() can be invoked multiple times during the validation process: it is important to create the delivery note only after the stock_move.quantity_done values has been updated otherwise delivery note and picking will be misaligned.
d3b9b6f
to
4a49a7d
Compare
/ocabot merge patch |
This PR looks fantastic, let's merge it! |
Congratulations, your PR was merged at 8a0a8d8. Thanks a lot for contributing to OCA. ❤️ |
I documenti di trasporto generati utilizzando la modalità Base e lasciando che sia Odoo ad impostare le quantità completate nel trasferimento (You have not recorded done quantities yet, by clicking on apply Odoo will process all the quantities) riportano le quantità prodotto erroneamente a 0.
Il problema nasce dal fatto che all'intero del metodo stock_picking.button_validate() la creazione del documento di trasporto precede l'aggiornamento delle quantità completate nel trasferimento di origine.
Passi per riprodurre la problematica su Runboat: