-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
[15.0][ADD] stock_delivery_sale_section_and_note #293
[15.0][ADD] stock_delivery_sale_section_and_note #293
Conversation
364b502
to
9110822
Compare
Depends on -> OCA/sale-reporting#235 |
0622ffd
to
70ada10
Compare
70ada10
to
f506684
Compare
…eporting into merge-branch-3157-master-8afc8d95
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
Hello @OCA/logistics-maintainers , your reviews are welcome |
Hi @StephaneMangin could you attend @leemannd comment about temporary reference ? |
_name = "stock.move" | ||
_inherit = ["stock.move", "display.line.mixin"] | ||
|
||
sequence = fields.Integer(related="sale_line_id.sequence", store=True) |
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 concern is about this line.
It is highly tight on sale line presence. If the delivery is generated from another flow, how does this behave ?
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
This module provides the propagation of sale order sections/notes lines to the delivery slip reports.