Daily updates from Odoo
Thursday, April 17, 2025
6 changes · 18.0
Enhancements to existing features
Invoice batch sending now shows more accurate counts based on the delivery methods that can actually be used for each invoice. Peppol invoice handling is also more reliable, including better behavior when invoice formats are missing and clearer treatment of blocking send errors.
Original PR description
### [IMP] account: fix the summary of account.move.send.batch.wizard *: account_peppol, snailmail_account The summary was displaying wrong numbers of invoices. Indeed, it was computed on default…
### [IMP] account: fix the summary of account.move.send.batch.wizard *: account_peppol, snailmail_account The summary was displaying wrong numbers of invoices. Indeed, it was computed on default methods, instead of methods that are applicable to the move. For example, if a move was not possible to send through Peppol because the partner is not registered on the network, it was still displayed in the summary of the batch sending (then not used when the async processing happened). We also always put email as a fallback, even if no email is set, since it can be added through the wizard. task-no (review with TSB/PMAX) ---------------------------- ### [FIX] account_peppol: Remove 'skipped' state of Peppol moves This state doesn't really make sense. It only happens when there is an error while generating the XML file to send, which can be considered as a blocking error. task-no ---------------------------- ### [FIX] account_peppol: fix batch send of Peppol invoices when no format set In previous commit[1], we set the BIS3 format on invoices that were meant to be sent trough Peppol, even if no invoice_edi_format was set on the Partner. This commit fixes some cases when sending multiple invoices with no invoice_edi_format but Peppol as default sending method ended up not being sent. [1]: https://github.com/odoo/odoo/commit/84a0b81a258262e3bb9dbaa9c9f37796303a9dad task-no
This pull request bundles several usability and reliability updates across Odoo, including clearer product availability for delivery and click-and-collect, better payment deletion guidance, corrected POS receipt links, and improved messaging membership behavior. These changes reduce customer-facing errors, improve staff workflows, and make reports and website interactions behave more consistently.
Original PR description
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
This change adds a reusable way for Odoo to find the default sale orders linked to a process. It makes future customizations easier and safer for businesses that extend sales workflows.
Original PR description
in this commit: - added a helper function to get sale order ids which can be override in inherited models. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product forms now avoid loading a very large Intrastat code list into the browser. This reduces memory use and helps users navigate product records more smoothly, especially in databases with many Intrastat codes.
Original PR description
Previously, the intrastat_code_id was filtered by checking against a large list that is sent to the frontend. This caused huge memory usage due to the list being used in many objects and the list itself being large, around 10k items. This memory leak caused slowness in the frontend while going through the product form views. Currently, the list is not being sent. The domain itself is evaluated from the frontend without sending a list. This reduces memory footprint and slowness.
The Knowledge portal search experience has been adjusted so results better match whether users are searching from the portal or the main back office. This should make it easier for portal users to find the right articles without seeing less relevant internal results.
Helpdesk tickets that include billable timesheets can now be invoiced more easily once they are solved. Timesheets are automatically validated when a ticket reaches the solved stage, and a new Create Invoices action in the helpdesk overview helps teams bill completed work faster and with fewer manual steps.
Original PR description
Before this commit : - Timesheets are not validated automatically when a ticket is solved . - No available button to create invoices for solved tickets in the helpdesk overview. After this commit: - Timesheets linked to a helpdesk ticket get validated when ticket is moved to Solved stage. - A 'Create Invoices' button is added to invoice solved tickets in helpdesk overview. Task id: 4243781