Thursday, March 27, 2025
3 changes · 18.0
Enhancements to existing features
Batuz electronic invoicing responses now show both the general response status and any detailed error information found in the response content. This helps users and support teams understand submission problems faster and resolve them with less back-and-forth.
Original PR description
Before version 18, even if the response was Incorrect in the headers, it would still process the XML itself to see if e.g. there was a more detailed error message in there. Here, we just add the errors together again: the one from the header and the one from the response. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Opening the Replenishment view is now much faster in databases with many automatically managed stock rules. The change avoids unnecessary quantity calculations when there are no manually triggered items to clean up, reducing delays for inventory users.
Original PR description
Issue --> When the Replenishment view is opened, the method `_unlink_processed_orderpoints` is called to remove previously automatically created orderpoints that have since been refilled. In this…
Issue -->
When the Replenishment view is opened, the method `_unlink_processed_orderpoints` is called to remove previously automatically created orderpoints that have since been refilled. In this method, the search domain contains `qty_to_order` which causes computations to fulfil the search query. The search_query also contains `("trigger", "=", "manual")`. Even if the recordset for this leaf is 0, the `qty_to_order` computations still occur, only to return 0 records in the search.
Solution -->
Move the `qty_to_order <= 0` check after the search produces a recordset for `("trigger", "=", "manual")`. This avoids unnecessary computations.
Benchmarks -->
For this benchmark, we'll assume the worst case, where every orderpoint on the database has trigger set to `auto`. The number of seconds represents the time taken to open the Replenishment view.
| # of auto trigger orderpoints | Before | After |
|--------|--------|--------|
| 12.2k | 155.58 s | 4.49 s |
| 6k | 59.87 s | 3.78 s |
opw-4606704This change adds the CIM salary rule and related parameters for Luxembourg payroll. It helps ensure payroll calculations reflect the required tax credit treatment for eligible employees.
Original PR description
task-4577617