-
-
Notifications
You must be signed in to change notification settings - Fork 354
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][IMP] delivery_package_number: add field for auto printing #762
base: 16.0
Are you sure you want to change the base?
Conversation
@pedrobaeza anyone from tecnativa to review/give opinion on this please? This is due to the last pr you merged #750 |
3a2e4fb
to
5e87df5
Compare
@sergio-teruel @CarlosRoca13 didn't you develop something similar on v15? |
Yes!!1 |
@ferran-S73 please check 15.0 commits and put this branch up to date with it, and you'll have the feature. |
@pedrobaeza @sergio-teruel I can't seem to find the feature you guys are talking about on v15. Could you point towards which commit is missing please? |
@pedrobaeza @sergio-teruel just to clarify this a separate field to decide whether the report number of packages should be printed on picking validation, I didn't see any similar feature in any past version. If it does exist could you help me find it? |
Hi Ferran, if you follow this steps in v15 or v16 (it was migrated yet). You can test the feature by doing this steps:
|
Hi @CarlosRoca13 , thank you for the explanation but that isn't the point of this PR. What we want is to not automatically print the report when the picking is validated through any of it's wizards. That is due to those wizards using the base 'print_label' field and the reason I opted for adding a new field. Yo can try for yourself just validate a picking through a wizard (validate it partially for example) without the force set number of packages field and you'll end up with the report number of packages printed if the print_label field is checked. |
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. |
@CarlosRoca13 @pedrobaeza could you review please? |
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. |
5e87df5
to
731f1a1
Compare
731f1a1
to
9a9f536
Compare
@pedrobaeza @CarlosRoca13 could you review my last comment please? |
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
@rousseldenis could you remove the stale label please? |
I'm testing what you're saying on a runbot, but I'm not getting any kind of report. I'm not sure if I'm fully understanding what you mean. If you would be so kind, could you please provide a step-by-step list of what I need to do in order for what you don't expect to happen and what you do expect to happen? |
@ferran-S73 FYI there is : OCA/stock-logistics-reporting#347 |
I know this may be a bit counterintuitive but the print_label base field is used for sending to shipper so making these labels auto printed by this field has caused an issue in some clients that want to have the shipper feature but don't want the number of packages label.
Best way I've found to resolve the issue is by creating a dedicated field to configure the auto-printing.