-
-
Notifications
You must be signed in to change notification settings - Fork 649
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
[14.0][IMP] stock_picking_invoice_link #1010
[14.0][IMP] stock_picking_invoice_link #1010
Conversation
The quantity being compared is a product quantity, and not a currency amount, so it must not use the rounding of a currency but instead the precision of Unit of Measure
76ebdf9
to
ce51dc8
Compare
relation="account_invoice_stock_picking_rel", | ||
column1="account_invoice_id", |
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.
IMO we don't want to keep these values (using the defaults must be enough)
51adb80
to
eff5390
Compare
eff5390
to
a4fcdcd
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.
LGTM 👍
a4fcdcd
to
c58103e
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.
add the complete name of addon to the PR name and commits message stock_picking_invoice_link
@@ -3,7 +3,7 @@ | |||
<!-- Copyright 2013-2014 Alexis de Lattre <[email protected]> | |||
License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl). --> | |||
<record id="invoice_form" model="ir.ui.view"> |
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.
<record id="invoice_form" model="ir.ui.view"> | |
<record id="view_move_form" model="ir.ui.view"> |
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.
this record id already exists in: https://github.com/OCA/stock-logistics-workflow/blob/14.0/stock_picking_invoice_link/views/stock_view.xml#L24
so i get:
[W7902(duplicate-xml-record-id), ] Duplicate xml record id "data/view_move_form_noupdate_0" in views/account_invoice_view.xml:5
i added "_inherit" postfix to avoid issues.
This PR has the |
5dd7704
to
09c8aff
Compare
09c8aff
to
f41fb82
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.
My fears of #816 (comment) are still there
@pedrobaeza the problems emphasized in #816 (comment) is reasonable, but this PR doesn't touch that part of the code, this improvement to other parts of the addon |
Please check latest changes on 13.0 version, that should cover all the possible cases. The latest one arrived with #750. We should forward-port that changes instead. If there's something still uncovered, please comment. |
/ocabot migration stock_picking_invoice_link |
The migration issue (#708) has been updated to reference the current pull request. |
@pedrobaeza It's too bad I didn't got back to this PR during these OCA days to be able to talk about this issue together with you, and I'm not in Brussels but in the train on my way back to Switzerland. I just tried the last changes that were merged in 14.0, but moves for product with ordered quantities are actually still not linked to the invoice. About what you mentioned in #816 (comment) , to me the biggest issue was the change to a computed field instead of having everything stored, but it was already done some times ago. Then you guys have been adding considerations of return moves to credit notes in #1100 which to me is the same kind of change of adding the support of ordered quantities. Then AFAIU you also agreed in #989 (comment) that it doesn't make sense to keep this as a separated since the breaking change (i.e. the change to a computed field) was already merged. Now, we will still need to rebase this PR and fix all the conflicts properly to consider the last changes that were done, but I don't want to spend any more time on this if the feature is going to stay in an unmerged PR. Can we agree that we're going to merge this after rebase or should we better fix and merge #989 ? |
ping @pedrobaeza |
@CarlosRoca13 can you check? |
ping @CarlosRoca13 🙏 |
Sorry for not saying anything about it in this PR, We add the support to ordered quantities in this commit 0bd063a, you can check it and add any improvement that you need 😄 |
@CarlosRoca13 No worries, at least the feature is now available out of the box in the module and we don't need to spend any more time on it. @ajaniszewska-dev We can then close this PR. |
port changes from #816