A Dissabte 17 Agost 2013 19:03:16, oscar_alvarez va escriure: > 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?
This bug is in the bugtracker, and there's a solution proposed by Cédric. To be implemented. https://bugs.tryton.org/issue3173 > 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.¿? If it is derived from the first problem, fixing that one fixes this one too. You may also create a module which simply avoids creating two variants from one template if that is the need of your customer. > 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. As I said if you only need one variant per template, you can create a module that shows it as if it was only one. You can also create a function field in template that searches in the variant's code. > 4. The coding with two models product.product and product.template add a > little complexity for develops new modules. Agreed. Basically one needs to put things in template generally and you may need to move some fields to variants for some of your customers. This happened to us with supplier prices, for example. > 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. Did you mean "I found *no* real/important useful for product variant"? We've found it useful in several industries while it is more an annoyance in other ones. Basicallly those in which there are no variants. -- Albert Cervera i Areny Consultor funcional Tel. 93 553 18 03 @albertnan www.NaN-tic.com Avís legal >>
