Monday, November 24, 2025
5 changes · 18.0
Enhancements to existing features
This change speeds up how product details are loaded during sales product configuration by fetching related data in batches instead of one by one. It reduces waiting time significantly, especially when products have many attributes and values, making the experience smoother for users.
Original PR description
Performing read operations on attributes and values in batch yields a significant performance improvement and is standard practice. Tested with 60 attributes and 8000 values: went from 2.7s to 0.8s (-70%) No task --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Importing journal items will now accept lines linked to inactive accounts instead of failing with an unnecessary error. This makes data imports smoother when historical or temporarily disabled accounts are still referenced in the source file.
Original PR description
When importing journal items, if an item targets an inactive account, the import is causing an excessive error. We shall ignore the active/inactive flag in such a case. task-5350113 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update changes how Odoo sends messages to IoT Boxes so each device gets its own message instead of a combined one. It helps ensure delivery and reporting features continue to work reliably with stable IoT Box versions.
Original PR description
In order to ensure ws compatibility with stable IoT Boxes versions, we now split websocket messages to send one per IoT identifier, instead of one targeting multiple ones. related: odoo/odoo#234175 Forward-Port-Of: odoo/enterprise#100127
This change lets users import journal items that reference inactive accounts without the import failing. It prevents unnecessary errors and makes data imports more reliable when older or archived accounts are involved.
Original PR description
When importing journal items, if an item targets an inactive account, the import is causing an excessive error. We shall ignore the active/inactive flag in such a case. task-5350113 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo now uses the newer invoice generation logic by default for more BIS3-based electronic invoice formats. This reduces the risk of inconsistencies across country-specific formats and helps keep maintenance simpler and more reliable.
Original PR description
Since commit 52e984037 we have enabled the new helpers by default for generating BIS3 UBLs. But we didn't enable them in the UBL formats that depend on BIS3 (NLCIUS, XRechnung, Chorus Pro etc). That was to first fix any issues in BIS3 in case the new helpers had broken something. Since the new helpers seem to be working fine for BIS3, we are now making them the default for all the formats that depend on BIS3 as well. We also add comments in the old helper methods to indicate that they are no longer used by default for BIS3 and its extensions. task-none