-
-
Notifications
You must be signed in to change notification settings - Fork 605
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][FIX] pos_order_to_sale_order #1065
Conversation
Hi @legalsylvain, |
af6760e
to
c5673c1
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.
In default module behavior product internal reference in sol is not displayed. Now products Internal reference is displayed. |
Thanks for the explanation ! Well, the problem IMO is that this PR introduce a useless field at sale.order.line level that will take space in the DB. We should consider another design. I guess call |
Hello @legalsylvain ! This function (_get_sale_order_line_multiline_description_sale) is called after created SOL, so at preparing value I think better solution adding new field for saving customer_note. |
I think you can pass information by context. It could make the job. |
Hi @legalsylvain we have approached this problem from another angle) Could you have a look please? |
Hi. I'm on holidays the next week. I'll take a look when I'm back to the office. |
Thank you! Have a nice holidays) |
At creating SO from pos, description computed by default with adding customer note from POS.
a96796a
to
0188833
Compare
@@ -1,6 +1,7 @@ | |||
* Go to Point Of Sale / Configuration / Point of Sale | |||
* Check the box 'Create Sale Orders' | |||
* Select the desired default behaviour | |||
* Select the SO Line Name mode |
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.
Select Sales Order Lina name composition mode
@@ -0,0 +1 @@ | |||
Sale order line description computed by default with adding Customer note. |
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 is not a bug. A feature is being added.
Add readable and clear feature description please
("multiline", "Sale Multiline Description"), | ||
], | ||
string="SO Line Name Mode", | ||
default="product_pos", |
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.
What happens if user will remove selection value? So no option is selected
…efault value for config paramenter is changed.
c0f0d57
to
fc3ab80
Compare
Hi @legalsylvain sorry for bothering you again) Would be great if you could have a look at this |
product_name = product.name | ||
product_name += "\n" + order_line_data["customer_note"] | ||
vals.update(name=product_name) | ||
return vals |
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.
Maybe I'm wrong, but it looks like if the previous condition is wrong, the vals returned doesn't contain any "name" value. Did I missed something ?
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.
Maybe I'm wrong, but it looks like if the previous condition is wrong, the vals returned doesn't contain any "name" value. Did I missed something ?
Thank you for you question!
Name field is auto complete after creating SOL. And this solution for the set custom value for SOL description.
Hi @geomer198.
I don't think so. I made an alternative implementation here #1080. Thanks for you review. |
Thanks for your solution. |
At creating SO from POS, description computed by default with adding customer note from POS.