Tryton - Issues

 

Issue6799

Title suppliers don't relate to product variants
Priority feature Status chatting
Superseder Nosy List ced, risto3
Type feature request Components
Assigned To Keywords
Reviews

Created on 2017-10-01.19:41:01 by risto3, last changed by risto3.

Messages
msg36119 (view) Author: [hidden] (risto3) Date: 2017-10-06.18:51:26
The only thing is that by default the supplier should use the 'default' product which today should probably always be the first product [variant] (OpenERP had a sequence?).
That is, of course, only until another product is specifically selected.
msg36116 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2017-10-06.18:18:21
Indeed I think a good solution will be to add on the product supplier a second optional field for the variant (aka product). Of course both values should be kept coherent with a domain constraint.
On the variant (aka product), we should add a product_suppliers field which use this new field and add a product_supplier_used property (like for accounting) which return the product values if not empty or the template values not linked to another product.
msg35985 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2017-10-01.19:50:32
Not a bug, it is how product supplier is designed. It links the template and not the product. This is the pattern in Tryton to define on template by default and allow customization at the product level.
msg35984 (view) Author: [hidden] (risto3) Date: 2017-10-01.19:41:00
I created a very simple product with variants on demo4.4.tryton.org
called 'PRESTO 605 sur plage'.
The variants are 'Eau froid' and 'Eau chaude'.
I created two suppliers each providing both products.

Unfortunately the suppliers codes seem to always map to the first variant
'Eau froid' so it is quite apparent that there should be a means to 
relate the suppliers products to the correct product variant.

Though it seems that it has been mentioned before, there is a missing variant
specific name needed, though the description seems somewhat there.
History
Date User Action Args
2017-10-06 18:51:26risto3setmessages: + msg36119
2017-10-06 18:18:21cedsetmessages: + msg36116
2017-10-01 19:50:32cedsetpriority: bug -> feature
status: unread -> chatting
type: feature request
messages: + msg35985
nosy: + ced
2017-10-01 19:41:01risto3create

Showing 10 items. Show all history (warning: this could be VERY long)