Odoo Changelog — 2026-05-16

Saturday, May 16, 2026

4 changes · saas-19.3

Bug Fixes(4)

Resolved issues and error corrections

[FIX] planning_field_service_sale_worksheet: load demo worksheet data

Enterprisesaas-19.3planning_field_service_sale_worksheet

This update fixes an issue where demo data didn't correctly populate the 'Device Installation and Maintenance' worksheet for Field Service products. By loading product demo data, the system now automatically assigns the appropriate worksheet, ensuring demo data is accurately represented.

Original PR description

Load product_product_demo.xml in the 'planning_field_service_sale_worksheet' module so that the `Device Installation and Maintenance` worksheet is correctly set in Field Service product when demo data is loaded, instead of using the default worksheet.

Forward-Port-Of: odoo/enterprise#117407

#demo data#worksheet#field service

[FIX] orm: optimize tautology before calling search

PR #264845

Coresaas-19.3orm

This update optimizes how Odoo handles boolean searches, specifically when searching for fields that can be True or False. By moving the optimization step earlier in the process, Odoo ensures compatibility with various search implementations, leading to more reliable and efficient search results. This change improves overall system performance.

Original PR description

When optizing `('searchable_bool_field', 'in', [True, False])`, the optimization for the tautology is called after the search method. We should do it before as this case may not be handled by implementations which always expect `'in'/'not in', [True]`.


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#264636

#performance#search#optimization

[FIX] registry: commit resetting module state

PR #264768

Coresaas-19.3base

This update addresses a potential instability issue during module upgrades. When an upgrade fails, a process is now initiated to reset the module's state and commit the changes before re-raising the error. This ensures a cleaner and more reliable upgrade experience for users.

Original PR description

If we fail to upgrade modules, we call `reset_module_state`, but this needs to be committed before re-raising the exception.

Introduced in e6bcdfb92f1f0c39ec69d15d7c683d3f93573fa8.


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#upgrade#stability

[FIX] hr_expense: fix payment of multiple expense bills

PR #264823

Coresaas-19.3hr_expense

This update resolves a technical error that prevented multiple expense bills from being paid correctly. The issue stemmed from incorrect data being passed during payment creation, specifically related to bank account information. This fix ensures that multiple expense bills can now be paid without errors.

Original PR description

**Steps to reproduce:**
- Install Accounting and Expenses

- Create an expense:
  * Category: [any]
  * Total: [any]
  * Employee: [create or select one without a bank account]
  * Paid by: Employee (to reimburse)
- Submit
- Post Journal Entries (in Purchases journal)
- Create another expense, submit it and post its journal entries

- Go to the bills list
- Select both bills created from the expenses
- Click on "Pay" and then on "Create Payments"

**Issue:**
A traceback is raised while creating a payment.

**Cause:**
In the values used to create the payment, "partner_bank_id" is an empty "res.partner.bank" recordset instead of False, which leads to a SQL error because the type of the value is invalid.

opw-6206315




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#263841

#payments#expenses#accounting

Load product_product_demo.xml in the 'planning_field_service_sale_worksheet' module so that the `Device Installation and Maintenance` worksheet is correctly set in Field Service product when demo data is loaded, instead of using the default worksheet. Forward-Port-Of: odoo/enterprise#117407

When optizing `('searchable_bool_field', 'in', [True, False])`, the optimization for the tautology is called after the search method. We should do it before as this case may not be handled by implementations which always expect `'in'/'not in', [True]`. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#264636

If we fail to upgrade modules, we call `reset_module_state`, but this needs to be committed before re-raising the exception. Introduced in e6bcdfb92f1f0c39ec69d15d7c683d3f93573fa8. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

**Steps to reproduce:** - Install Accounting and Expenses - Create an expense: * Category: [any] * Total: [any] * Employee: [create or select one without a bank account] * Paid by: Employee (to reimburse) - Submit - Post Journal Entries (in Purchases journal) - Create another expense, submit it and post its journal entries - Go to the bills list - Select both bills created from the expenses - Click on "Pay" and then on "Create Payments" **Issue:** A traceback is raised while creating a payment. **Cause:** In the values used to create the payment, "partner_bank_id" is an empty "res.partner.bank" recordset instead of False, which leads to a SQL error because the type of the value is invalid. opw-6206315 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263841