Daily updates from Odoo
Wednesday, August 6, 2025
3 changes · master
Resolved issues and error corrections
Sales achievements made on the final day of a commission period are now included in the correct commission calculation. This prevents end-of-month sales from being missed, improving accuracy for commission reports and payouts.
Original PR description
**Issue** Achievements realised on the last day of the period were not taken into account (neither in the expected one, or the next period). **Steps to reproduce** - Create a commission plan with a monthly target frequency and an achievement on "Amount sold" - Have a Sale order with a `date_order` on the last day of a month - Click on the "Commissions" smart button to open the `sale.commission.report` list view -> achieved amount for the SO's month is missing. - Click on "Details" for the line -> there should be one `sale.commission.achievement.report` record. **Cause** We were comparing a Timestamp coming from the commission line with the start/end date of the period. To perform the comparison, the date was cast to a Timestamp with 0:00:00 as the hour, resulting in all commission lines on the last day of the period to be missed. opw-4857936 opw-4934168 Forward-Port-Of: odoo/enterprise#91707 Forward-Port-Of: odoo/enterprise#90658
Customers can now choose supported shipping carriers at checkout when their order includes combo products, as long as the combo items have weights set. This also avoids incorrect missing-weight warnings for non-shippable order lines such as down payments, reducing checkout and sales order friction.
Original PR description
\* = bpost, dhl{,_rest}, easypost, sendcloud, ups, usps{,_rest} Versions -------- - 18.0+ Steps ----- 1. Have a combo product Foo; 2. ensure the combo items have a weight set; 3. enable & publish a…
\* = bpost, dhl{,_rest}, easypost, sendcloud, ups, usps{,_rest}
Versions
--------
- 18.0+
Steps
-----
1. Have a combo product Foo;
2. ensure the combo items have a weight set;
3. enable & publish a shipping connector;
4. add combo product to cart;
5. go to checkout;
6. attempt to select shipping connector as delivery method.
A similar message appears when trying to add a delivery method to a backend order if the order has downpayment lines.
Issue
-----
> The estimated shipping price cannot be computed because the weight is missing for the following product(s): Foo
Cause
-----
The combo product doesn't have a weight, as it's not a discrete item, but a collection of multiple items.
The shipping connectors haven't been updated yet to account for this, and still expect every non-service product to have a weight.
Solution
--------
When looking for lines without weight, filter out products of type `combo` (similar to how `service` products are handled) using a new `_get_invalid_delivery_weight_liens` helper method, added to `sale.order.line`.
Also ignore lines where `product_qty` is zero, e.g. `display_type` lines & down payment lines.
Community PR: https://github.com/odoo/odoo/pull/221696
opw-4940973
Forward-Port-Of: odoo/enterprise#91684
Forward-Port-Of: odoo/enterprise#91243Embedded accounting reports in Knowledge templates now include the identifier needed to save customized report options. This ensures users can adjust reports such as the Balance Sheet in an article and see those changes preserved when they return.
Original PR description
Currently, the embedded account reports included in templates are missing the `data-oe-id` attribute. This attribute is essential because it allows us to uniquely identify and target a specific…
Currently, the embedded account reports included in templates are missing the `data-oe-id` attribute. This attribute is essential because it allows us to uniquely identify and target a specific report element in order to update its associated options. (See: `update_embedded_audit_report_options`) Without this attribute, we are unable to locate and update the corresponding element in the DOM when the user customizes the report. As a result, users are unable to save changes to the report options for embedded reports originating from templates. Steps to reproduce the issue: 1. Create an account report 2. Open the "Balance Sheet" article 3. Click on the "Customize" button of the embedded balance sheet 4. Change the options (in the control panel) 5. Go back to the article 6. Re-Click on the "Customize" button => Changes have not been saved TO BE: When a user clicks the "Customize" button of an embedded account report and modifies the options, those changes should be saved. To resolve this issue, we will add a `data-oe-id` attribute to the embedded account reports defined in the templates. With those changes, users will be able to modify and save the options of audit reports embedded in templates. Task-4840940