[17.0][MIG] sale_variant_configurator: Migration to 17.0 #381
[17.0][MIG] sale_variant_configurator: Migration to 17.0 #381BhaveshHeliconia wants to merge 25 commits into
Conversation
46ad458 to
bf9f532
Compare
bf9f532 to
cec0d65
Compare
|
Please, cherry-pick #395 to commit history (before migration) |
cec0d65 to
4a140b5
Compare
|
@victoralmau, Please Review! |
|
Please, cherry-pick #398 to commit history (before migration) |
76e28be to
7b59806
Compare
|
@victoralmau, Please Review.It's done. |
7b59806 to
2b424d1
Compare
|
@victoralmau, Please Review all changes.it's done. |
2b424d1 to
406f6fb
Compare
|
@victoralmau, Please Review.it's Fixed. |
|
/ocabot migration sale_variant_configurator |
pedrobaeza
left a comment
There was a problem hiding this comment.
You are destroying the previous README contents. You should transfer description, contributors, etc to the new fragment system.
|
https://github.com/OCA/product-variant/tree/16.0/sale_variant_configurator |
|
As said, you have to transfer the contents of the previous README.rst to each fragment of the |
406f6fb to
2fc2cdb
Compare
|
@pedrobaeza, Please review the updated README folder. |
2fc2cdb to
14fc5f4
Compare
This comes from module sale_product_variants from odoomrp/odoomrp-wip.
- saleable products for Sale Orders. - purchable products for Purchase Orders.
Depending on the onchange order loaded in runtime, description put in the SO line might be the one got from the regular way. With this, we assure we get the proper description, and also in the partner language (using the trick with the partner field).
* Use generic method for creating the variant if needed * Create the variant when the sales is already confirmed
for some reason, after the creation of the product, the sale.order.line was emptied (e.g. product_tmpl_id was False) -> the onchange would do nothing. I split the test in two, and in the second test, I create the product before creating the sale order line.
…omer language As the model `sale.order.line` doesn't have `partner_id` field, the description is not populated in the customer language, as the automatism put in product_configurator makes use of this trick. For not adding such field that can conflict with other parts, let's overwrite the methods that populate the description and pass upstream the customer language in the context. TT33029
Currently translated at 100.0% (8 of 8 strings) Translation: product-variant-16.0/product-variant-16.0-sale_variant_configurator Translate-URL: https://translation.odoo-community.org/projects/product-variant-16-0/product-variant-16-0-sale_variant_configurator/pt_BR/
Steps to reproduce the error: - Go to Sales > Configuration and activate 'Units of Measure'. - Go to a quotation and add a line indicating a Product Template with several attributes (Conference Chair for example). - You must be able to select a unit of measure + the unit of measure is set automatically. Other versions (v13 for example) use another technique https://github.com/OCA/product-variant/blob/2922137d2de670010200fa0cb7cdf1469bffafbe/sale_variant_configurator/models/sale_order.py#L69 TT55223
…oduct_id field to filter correctly. TT57913
75ba32a to
cec4892
Compare
cec4892 to
9fbaf39
Compare

No description provided.