Created on 2021-04-01.17:13:58 by albertca, last changed 1 month ago by ced.
Idem for cost_price.
I think the proper solution is to reuse the same design as
account_used because for me it must raise an error if there is no price defined instead of using a default value (which will probably be zero).
To properly solve the issue all modules should be reviewed to ensure that they do not crash when the list price is not set. Then we can make the list price not required.
Although list_price field is defined as required in product.template:
This cannot really be enforced because it is MultiValue. So a product created from company A will have list_price set to NULL on company B.
This will cause crash on get_sale_price() if there needs to be a currency conversion:
I think we should:
messages: + msg67775
nosy: + ced
nosy: + pokoli
status: unread -> chatting
Showing 10 items. Show all history (warning: this could be VERY long)