You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make a buy/mto-product with an attribute of type range.
When a attibute of type range is involved, a purchase order line behavious differently depending on if the po line is entered manually or if it is placed by procurement.
When the po line is placed manually, the attribute table is shown and the range custom value can be entered.
Now enter the product in a so line and fill out the custom value. Start the procurement.
When the po line is placed by procurement, the attribute table is not shown in the po line, and hence the custom value is not shown either. Unlike issue #1163 however the procurement does not produce an error.
IMHO, it would be best to add the product configurator attribute table also in procurement. I think it would be clearer and both this issue and issue #1163 could be solved consistantly. This could be done in two modules procurement_product_variant and procurement_product_variant_types.
Tested on
demo.odoomrp.com
db=September_2015_EN
The text was updated successfully, but these errors were encountered:
Make a buy/mto-product with an attribute of type range.
When a attibute of type range is involved, a purchase order line behavious differently depending on if the po line is entered manually or if it is placed by procurement.
When the po line is placed manually, the attribute table is shown and the range custom value can be entered.
Now enter the product in a so line and fill out the custom value. Start the procurement.
When the po line is placed by procurement, the attribute table is not shown in the po line, and hence the custom value is not shown either. Unlike issue #1163 however the procurement does not produce an error.
IMHO, it would be best to add the product configurator attribute table also in procurement. I think it would be clearer and both this issue and issue #1163 could be solved consistantly. This could be done in two modules procurement_product_variant and procurement_product_variant_types.
Tested on
demo.odoomrp.com
db=September_2015_EN
The text was updated successfully, but these errors were encountered: