On 2017-10-16 07:49, Thierry Bruyere wrote: > I do not understand why the "list_price" field is in the "product" module.
It is a legacy. > If I understand the "list_price" field is the selling price of a > product (sales price). By default, yes. > This field is mandatory by default on the creation of an article not > sold / not purchased / consumable -> still mandatory > We are obliged to define a "selling price" for all products. You can put it as zero if you do not have one value. But it was useful to have it required because it avoid to have to test in many places. We did not put a default value because we thought it will be too much error prone. Now, I think as it is a MultiValue, we can not really guarantee that the a price will be set for all condition (multi-company etc). So we can have a careful review of the code and fix cases that rely on the field being required. Then we could remove the required constraint. > The "list_price" field is used in a view on the purchase module to > display the selling price relative to the unit for the choice of a > product to be added in a purchase > (line.modules/purchase/view/product_list_purchase_line.xml:). > I do not understand why the purchase department should see the selling > price? In addition, the product may not be sold (production) or for > internal consumable (computer equipment, office equipment ...)) We have though it will be useful to make the decision of buying or not depending on the margin made. > It is normal to find the "list_price" field used in the sales modules > (sales, project_revenue,project_invoice,carrier,stock->move) > > Why is this field not added by the sales module? > But the module "sales" is not a dependent for modules : > project_revenue, project_invoice, carrier. You just find the answer. > And why this field is not mandatory only in the case of a product > Salable (but the same remark is present for the other modules using > this field) ? The field is for a more generic usage so it is simpler to have it in product module. > Do I always set the value to 1 or 0? ((and why not make a personal > custom to set this field to 1 when I creating an article)) I would not use 1 as value because it is completely arbitrary. But having a default value of 0 may lead to forget to fill it for salable products. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/20171016153756.GH3623%40kei.
