Hi devs, I have been thinking from some month's ago, if it separates products and variants is a good idea as today is on Tryton 2.8..., so now I have clear it, after of work with my customers/end users and development some not offcial modules, so IMHO that is not good idea although in principle it seem yes, I found some problems with this:
1. The first when you try add new product in sale line and click in search record the products apparently twice (this seems a bug, but I believe doesn't it), how do you choose the exactly product (without code) if two products is named same in the list, but you only has created one? 2. The first problem cause the second problem, when you try coding a new model with cls._sql_constraints with field "product" as UNIQUE, choose for the right product in list window is complicated for the end user because the product appear twice, in my testing process with this example | Template | Code | ..... | | PRODUCT_A | | | | PRODUCT_A | | | with a first item "PRODUCT A" the constraint is triggered, but with the second it isn't.¿? 3. The code field in some companys is very important for search products in the system, but this field was deleted from product.template view tree in favor of product.product (variants), so but tree view of product.product doesn't all information as product.template, if a user is searching product by code but needs quickly all info about the product have to do the process in two steps, so in 2.6 and previous versions just it was in a one step. 4. The coding with two models product.product and product.template add a little complexity for develops new modules. 5. My costumers are of the different companys/industries with a huge quantity products, but nevertheless I found a real/important useful for product variant. I am not want convert this topic in a discussion about ¿How it have reason?, maybe I am in a mistake, but I think that is important analyses about the problems mentionated.
