Daily updates from Odoo
Friday, November 21, 2025
6 changes · 17.0
Enhancements to existing features
The Japanese state records have been updated to use their native Japanese names directly, which improves how location names appear to users. The state codes were also aligned with ISO standards to keep the data more consistent and reliable.
Original PR description
Since state names are not handled by translations, storing them directly in Japanese provides a better user experience. This **PR** updates the existing Japanese state records with their native Japanese names. Additionally, it aligns the state codes as per ISO standards. **task**-5345872
The subscription log now labels the previous status as “State Before” instead of “Subscription State.” This makes it easier for users to understand that the value shown is the state before an event happened, reducing confusion when reviewing subscription history.
Original PR description
The sale.order.log model includes a field named subscription state that records the state of the subscription at the moment an event occurs (i.e., the state before the change). To improve clarity for end users, this PR renames the column from Subscription State to State Before. task-5258195
The homepage now checks for updates less aggressively when a browser tab stays open for a long time. This reduces unnecessary traffic to the IoT Box and helps keep it responsive while still refreshing the page periodically.
Original PR description
In order to avoid spamming the IoT Box with requests to update the homepage when a tab is kept open, we now progressively delay the `/data` fetch during the first 30min to end up fetching only once every 30min.
This change allows invoice confirmation dates to align with the invoice date, instead of always using the posting time. As a result, businesses can safely backdate invoices without creating mismatches between Odoo and the Saudi e-invoicing system.
Original PR description
Previously, `l10n_sa_confirmation_datetime` represented the time where the invoice was posted, that meant that we could not backdate invoices, since it would cause disparity between what zatca receives and what we consider in odoo (i.e. `invoice_date`) This commit allows us to set the date component of `l10n_sa_confirmation_datetime` to the `invoice_date` so we can safely backdate invoices. task-5009969 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update changes how messages are sent to IoT Boxes so they are handled one device at a time instead of grouped together. It helps ensure compatibility with stable IoT Box versions and reduces the risk of connection issues for affected setups.
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
This update ensures Odoo includes the expected application information in payment requests sent to Adyen. It helps Adyen correctly identify the external platform, improving reliability of payment processing and reducing the risk of request issues.
Original PR description
Add applicationInfo to the payload sent to Adyen, ensuring that externalPlatform is correctly transmitted. A test was added to verify that applicationInfo is present in the payload and that the payment request succeeds as expected. task-5157863 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr