Wednesday, October 15, 2025
4 changes · saas-18.4
Enhancements to existing features
Opening the analytic distribution popup on invoice lines with many accounts now avoids unnecessary repeated data requests. This makes the popup load more smoothly and reduces waiting time for users working with complex analytic allocations.
Original PR description
Currently opening the analytic distrubtion popup on an invoice line creates N network requests per account set on the line. Steps to reproduce ----- 1. Edit the analytic distribution on an invoice line and add a lot of accounts 2. Open the popup again 3. A lot of web_read requests are made Issue ----- The display_name for the account and currency is not being passed to the field values in recordProps(), resulting in another fetch when each Field element is rendered. Solution ----- Pass account.accountDisplayName. The display name for the currency is actually not initially loaded by the client, but since that field is invisible, we can safely use an empty string. opw-5106219 Forward-Port-Of: odoo/odoo#231342
This update prepares Belgian POS blackbox communication for a future queue mechanism by adding a required IoT action and prompting users to update their IoT setup. It helps ensure POS installations are ready for the next improvement that will make blackbox communication more reliable.
Original PR description
This commit is the first of two which will introduce a queue mechanism in the communication between the POS and the blackbox. This commit adds an action to the iot and invites users to update their iot to be prepared for the next commit which will effectively add the queue mechanism and use the new action. Second part: https://github.com/odoo/enterprise/pull/90747 Forward-Port-Of: odoo/enterprise#96639
This update prepares Point of Sale IoT device communication for upcoming Chrome browser restrictions on local network access. It ensures Odoo can continue connecting to local IoT devices that use the odoo-iot domain, reducing the risk of disrupted POS hardware operations.
Original PR description
Enterprise PR: https://github.com/odoo/enterprise/pull/96850 Local Network Access restrictions will start shipping by default in Chrome 142. As part of this change, local requests will be allowed to use HTTP in an HTTPS context (gated by a browser permission prompt). This will work automatically when the IP is provided directly, however in the case of IoT we often use the odoo-iot DNS domain to resolve the IP. In this case, you must specify the option `targetAddressSpace: "local"` in the `fetch` request. This commit simply adds this change where appropriate. task-5157145 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#231543 Forward-Port-Of: odoo/odoo#231014
This update prepares Odoo IoT and Point of Sale IoT connections for upcoming Chrome browser changes. It helps ensure local devices such as printers, scanners, or other IoT hardware can continue to communicate reliably when accessed through Odoo's IoT domain.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/231014 Local Network Access restrictions will start shipping by default in Chrome 142. As part of this change, local requests will be allowed to use HTTP in an HTTPS context (gated by a browser permission prompt). This will work automatically when the IP is provided directly, however in the case of IoT we often use the odoo-iot DNS domain to resolve the IP. In this case, you must specify the option `targetAddressSpace: "local"` in the `fetch` request. This PR simply adds this change where appropriate. As part of this we have also backported the change from jquery -> fetch. task-5157145 Forward-Port-Of: odoo/enterprise#97166 Forward-Port-Of: odoo/enterprise#96850