Daily updates from Odoo
Wednesday, November 26, 2025
10 changes
2 changes
Enhancements to existing features
This update enhances the stability of our IoT Box integration by splitting websocket messages. Previously, messages targeted multiple IoT devices simultaneously, which could cause issues. Now, each message is sent individually, per device, ensuring smoother and more reliable communication.
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#100317 Forward-Port-Of: odoo/enterprise#100127
This update enhances the documentation for Odoo's resource and shared method usage within the html_builder and html_editor modules. The changes improve type definitions, ensuring better code clarity and maintainability, which supports future development and reduces potential errors.
Original PR description
backport of https://github.com/odoo/odoo/pull/236084
3 changes
Enhancements to existing features
This update ensures that the same optional fields related to vehicle information are consistently displayed on both Receipts and Vendor Bills. This improves data clarity and simplifies the process for users entering this information, aligning the user experience across different document types. It addresses a previous inconsistency identified in the system.
Original PR description
This commit ensures that the same optional fields are displayed consistently on both Receipts and Vendor Bills. Updated the visibility of the following fields: - vehicle_id (Vehicle) task-5349202 Forward-Port-Of: odoo/enterprise#100422
This update prevents the unintended expansion of multiple folders when dragging documents. A 1-second delay is now implemented before a folder expands, ensuring a smoother and less distracting user experience. This change reduces visual clutter and improves usability within the Documents module.
Original PR description
Previously, when dragging documents and hovering over a folder in the side panel, the folder was expanded immediately. This led to the unintended expansion of multiple folders. This PR introduces a 1-second delay before expanding a folder during drag-and-drop operations, and only that folder will be expanded where we hover for 1 second; if some folders were previously hovered, that will be ignored, improving usability and reducing unnecessary noise in the UI. Task-4982715
This update ensures that salary attachments are correctly marked as 'cancelled' when an employee is archived, providing a more accurate record of payroll history. A message is also posted in the chatter to document the cancellation, improving transparency and auditability. This change enhances data consistency within the HR payroll module.
Original PR description
When an employee is archived, the related salary attachment's - Set the salary attachment state to 'cancelled' to reflect the change. - Post a message in the chatter explaining the cancellation due to archiving. task - 4991281
3 changes
Enhancements to existing features
This update adds necessary account settings for Slovak tax groups within Odoo. Specifically, it incorporates tax payable and receivable account IDs, ensuring accurate accounting for Slovak VAT reporting. This change supports compliance with Slovak tax regulations.
Original PR description
This commit adds tax_payable_account_id and tax_receivable_account_id to all tax groups in Slovak tempalte. opw-5264511 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This pull request adds comprehensive Hoot tests for the UrbanPiper integration, ensuring its functionality is thoroughly validated. Additionally, several minor fixes were implemented, including improvements to receipt printing, timer display, and data handling within the ticket screen, enhancing the overall stability and accuracy of the system.
Original PR description
## 1. Hoot test
in this commit:
- add HOOT tests for components, model, screen, and service
- added test for methods in `order_info_popup` and `order_display`
- include tests for `pos_order`, `ticket_screen`, and `pos_store`
- add utility to generate UrbanPiper-filled order
## 2. minor fixes
in this commit:
- kept serialized data for receipt printing
- ensure timer does not display negative values
- correct variable usage in ticket screen to fetch proper props for display order
- revamp `getTime` method to use l10n time format
task: 5048312
Forward-Port-Of: odoo/enterprise#93780This update simplifies the bank matching interface for users primarily working with invoicing. It removes unnecessary account codes from the display name and adds a more user-friendly search option that utilizes account descriptions, making it easier for users to quickly find the correct bank accounts without needing extensive accounting knowledge.
Original PR description
See commits' description --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1 change
Enhancements to existing features
This update clarifies the tooltip for the 'Prices' setting in the configuration. Previously, it stated the setting couldn't be changed after an invoice. Now, it correctly indicates the setting locks once a journal entry is created, providing better guidance for users. This change improves understanding and reduces potential confusion.
Original PR description
This commit improves the tooltip of the Prices setting in configuration. The old tooltip "This setting cannot be changed after an invoice is created." is changed to "This setting locks once a journal entry is created." task-5354382 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1 change
Enhancements to existing features
This update ensures queries in our project accounting modules use fully qualified column names (e.g., `account_move.balance`). This clarifies data sources and prevents ambiguity, especially when joining tables like `account_move` and `account_move_line`. It also helps avoid confusion with custom module columns, leading to more reliable reporting and data accuracy.
Original PR description
Use fully qualified column names when constructing a query, more specifically, include the table that the column is originating from. The rule of thumb is that we always include the table name alongside the column name. In this particular case, the query will do a `JOIN` on `account_move` and there may be ambiguousness as to whether to take the `balance` column from `account_move` or `account_move_line`. The former column used to exist in the past and was likely kept for data retention purposes. Hence, there are still databases in 17.0 where `account_move.balance` exists. Another reason to include the table name is to prevent confusion with columns coming from custom modules. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr