Daily updates from Odoo
Monday, March 17, 2025
6 changes
3 changes
Enhancements to existing features
This update aligns the enterprise e-invoicing integration with a shared approach for fetching electronic invoices and notifying users when new invoices arrive. It helps prepare Odoo for consistent e-invoice workflows across Peppol and future localizations such as Nemhandel.
Original PR description
We start accumulating buttons for fetching electronic invoices and their statuses with different localisations. In addition to peppol, there l10n_tk and soon l10n_dk (with Nemhandel: https://github.com/odoo/odoo/pull/190474) which also needs such a button In addition to these buttons, we also need a standard way of notifying users when receiving einvoices for these different modules This commit just adapts enterprise function signature for the changes made in community related prs: - odoo/upgrade#7205 - odoo/odoo#197233 task-4457146
The IoT system now keeps its websocket connection open by default instead of only opening it for report printing. This simplifies future IoT features while keeping server load low because one shared connection is used per company.
Original PR description
We used to open the websocket channel between iot box and db only when a report was set, to opening a useless connection. In order to simplify the code and reduce complexity when using ws for anything else than printing a report, we removed this logic. Note that we only use one ws channel for all iot boxes on the same company, making the load very small. Upgrade: odoo/upgrade#7383 Task: 4648490
IoT device pages now offer a clearer interface and a direct way to test printer status from the database. IoT Box pages also include a status button that opens the box homepage, helping users check devices faster and reduce troubleshooting time.
Original PR description
Improved IoT Device UI and added a button to test printers (print status) directly from the IoT Device form, in order to ease quick testing from the db. Also added a status button on the IoT Box form view to redirect to the IoT Box Homepage. Community PR: [https://github.com/odoo/odoo/pull/201231](https://github.com/odoo/odoo/pull/201231) Task: 4640921
3 changes
Enhancements to existing features
This update improves how Point of Sale data loads when opening sessions. It helps reduce slow startup times that were blocking a customer upgrade, making cashier workflows more responsive.
Original PR description
18.0 backport of odoo/odoo#198123 We need the fix in 18.0 because a customer's upgrade is blocked because of slow loading speed of point of sale sessions. opw-4582980 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Dutch tax reporting settings now allow businesses to define custom start dates for tax closings. This gives companies more flexibility to align VAT or tax closing periods with their specific reporting needs.
Original PR description
opw-4592126
Custom financial report engines now handle grouping by related account fields in the same way as standard reports. This makes consolidation report setup more flexible, especially when multiple source-company accounts share the same code, and adds automated coverage to catch similar issues earlier.
Original PR description
Since odoo/enterprise@a94227b, it is possible in standard report engines to group by non-stored related fields. Thanks to this, it is now possible to greatly improve the configuration of…
Since odoo/enterprise@a94227b, it is possible in standard report engines to group by non-stored related fields. Thanks to this, it is now possible to greatly improve the configuration of consolidation reports, by grouping the move lines by account_id.code, then account_id.name, provided that non-stored related fields are added on account.move.line for those values. This way, it becomes possible to configure multiple accounts mapped to the same code, without having to ensure a 1 to 1 relationship between the accounts of the source and consolidating company. This, however, was only implemented for standard engines. Custom engines were not modified, and none of them did the proper call to _fields_to_sql, to ensure the join condition of the query is adapted to run this grouping. This commit adds it, together with a test ensuring the custom engines are all evaluated on runbot with a non-stored custom groupby, so that errors are spotted directly and the developers just don't have to remember this "by heart". task-4596355