- Create a service product with cost 0 - Create a sales quotation - Add the service product, change the cost to a positive quantity - Save and Confirm. Purchase Price (cost) will be reset to 0 opw-2481564 closes odoo/odoo#69966 Signed-off-by: agr-odoo <agr-odoo@users.noreply.github.com>
When installing sale_margin, the computed fields will be computed on existing sale.order and sale.order.line in database. On huge databases, the computation may take a lot of time, depending on the configuration (multi-company, multi-currency, ...) The current commit improves the computation of the purchase_price (recently changed to a computed field), by avoiding unnecessary currency conversions when possible (one less query to get the conversion rates). In a multi-currency database where the products have no cost defined (standard_price field), the sale_margin installation takes up to 50% less time. closes odoo/odoo#52338 X-original-commit: 3c9841d1aa4fc5b10012c8239a31d6e7f8676fc0 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Installing sale_margin module on a db with a lot of sale.order was impossible. This commit significantly improves performances. Went from many hours (forecasted) to 15 minutes on a db with 300k orders For sale.order: - Duplicating logic between edit mode and non edit mode - Edit mode logic stays the same as before - Non edit mode uses read_group to speed up the computation X-original-commit: 9f1ea7427cdb6984f175f5111e4c9a4c5f013af2
And use "Margin (%)" for the recently added margin_percent field computing the margin in % and not in money. closes odoo/odoo#43130 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Onchanges can be triggered after computes and therefore, we could have a line with an uom but without product, leading to a conversion from "no uom" to the order line uom, which isn't accepted. closes odoo/odoo#42691 X-original-commit: 1bc9963cfc19a4bc5896a647423f81274936db00 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
New field to express the profitability percentage of a Sales Order (/SO line). task-2033253 closes odoo/odoo#39926 Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>
Since the purchase_price is now computed, it may be triggered before an uom is set on the product line (onchanges may happen after computes). closes odoo/odoo#41808 X-original-commit: 9ebbdd24752a0ff1c1057fc533074555810ffa39 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
And clean the code mess. closes odoo/odoo#40953 Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>
When creating sale order lines from the matrix (sale_product_matrix), the purchase_price weren't computed No cleaner change has been found to ensure the cost is computed. Triggering all onchanges from the server side is quite tricky and dirty to do... closes odoo/odoo#40986 X-original-commit: 5c15b1310729129e390b455b0d1e0ac367f8dd69 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
* account, hr_contract, hr_expense, point_of_sale, sale_margin, website_sale_delivery, website_sale_wishlist digits only works on Float fields, on Monetary fields it has no effect: - The column_type of a monetary field is always numeric - It is not applied in `convert_to_column()` or `convert_to_cache()` - It is not part of `description_attrs`, so it will not be included in the output of `fields_get()` closes odoo/odoo#35336 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>