Wednesday, October 15, 2025
4 changes · saas-18.3
Enhancements to existing features
Opening the analytic distribution popup on invoice lines with many analytic accounts now avoids unnecessary repeated data requests. This improves responsiveness for users working with detailed analytic allocations, especially on larger invoices.
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
Updates point of sale and IoT-related browser requests so local devices such as IoT boxes and customer displays continue to connect as Chrome introduces stricter local network access rules. This helps avoid disruption for businesses using local hardware with Odoo POS after upcoming browser changes.
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#231468 Forward-Port-Of: odoo/odoo#231014
This update prepares Odoo Point of Sale IoT connections for upcoming Chrome Local Network Access restrictions. It helps ensure local IoT devices can still be reached from secure Odoo sessions when using the odoo-iot domain, avoiding disruption for businesses using connected hardware.
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#97124 Forward-Port-Of: odoo/enterprise#96850
Belgian point-of-sale blackbox messages are now queued, reducing delays during sales workflows and improving reliability when the device is busy or slow. This especially helps actions like pro forma sales where staff do not need to wait for an immediate blackbox response to continue serving customers.
Original PR description
In this commit, we introduce a queuing mechanism for blackbox messages to make all interactions with the blackbox faster and more reliable. This is particularly useful for messages that do not require the response from the blackbox to continue the workflow such as pro forma sales messages.