Skip to content
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

[8.0][purchase_product_variants_types] inconsistent behaviour manually vs. procurement #1167

Open
roedeorm opened this issue Mar 5, 2016 · 0 comments

Comments

@roedeorm
Copy link

roedeorm commented Mar 5, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant