-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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][MIG] sale_order_qty_change_no_recompute: Migration to 16.0 #2365
Conversation
…uantity has changed in sale order line
…hange The _origin trick is not valid, as it doesn't reflect the state before the onchange, only the saved copy (if any).
…ent onchange quantity and some possible related error in another addons.
Changing that field shouldn't trigger price recomputation as well. TT32663
…y_change_no_recompute
/ocabot migration sale_order_qty_change_no_recompute |
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.
I like this approach
This PR has the |
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.
Adding that field is an overhead that shouldn't be for something transient like this
A proper migration has been implemented in #2473, as this one only covers changes in the UI, not by code, and it uses an extra field with possible side effects, so closing. |
#2215