-
-
Notifications
You must be signed in to change notification settings - Fork 239
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] stock_picking_report_valued_sale_mrp: Migration to 16.0 #356
Open
aitoreizmendi
wants to merge
19
commits into
OCA:16.0
Choose a base branch
from
factorlibre:16.0-mig-stock_picking_report_valued_sale_mrp
base: 16.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[16.0] [MIG] stock_picking_report_valued_sale_mrp: Migration to 16.0 #356
aitoreizmendi
wants to merge
19
commits into
OCA:16.0
from
factorlibre:16.0-mig-stock_picking_report_valued_sale_mrp
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We want to consider backordered moves even if they're cancelled but not cancelled moves from cancelled orders, that must be filtered. Otherwise, they pullute the amounts computation.
Update/direct assignation should be used instead.
odoo.tools.convert.ParseError: "Element '<xpath expr="//tr[@t-foreach='o.move_line_ids']">' cannot be located in parent view
When the recordset comes from multiple picking we could get a wrong calculation of the mrp lines in the report when the conditions of same component for the same order line would apply. So for every picking we have to compute the kits valuations independently. TT33076
… in stock.move It was a related field in v13, but now it's only on the picking, so let's access to it in the code. TT50285
1c14313
to
af6cea0
Compare
af6cea0
to
bb4053c
Compare
RodrigoBM
approved these changes
Dec 10, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Standard migration