Odoo Changelog — 2026-04-17

Friday, April 17, 2026

7 changes · saas-18.4

Bug Fixes(7)

Resolved issues and error corrections

[FIX] appointment_google_calendar: prevent error while saving appointment

Enterprisesaas-18.4appointment_google_calendar

This update fixes a bug that prevented users from saving appointments when removing the organizer. The issue stemmed from a mismatch in data expectations within the Google Calendar integration. This change ensures smooth appointment creation and prevents errors related to data consistency.

Original PR description

Currently an error is generated when the user tries to save an
appointment as follows:
- Install the appointment_google_calendar module without demo data
- Create a new appointment as below:
      - Remove Organizer (user_id)
      - Set the Google Meet link inside VideocallURL, e.g., https://meet.google.com/aaa-aaa-aaa
- An error occurs in the log and a message is shown to the user when save the record
- Also, an error occurs when trying to preview `Appointment: Attendee Invitation`
  after creating appointment as follows:
      - Set the Google Meet link inside Videocall URL > save
      - Remove Organizer (user_id)

Error: 
```
test odoo.addons.mail.models.mail_render_mixin: Failed to render QWeb template for Mail Template: 'Appointment: Appointment Booked' (ID: 12) - Context language:en_US
Target Model: calendar.event
Error: Error while render the template
ValueError: Expected singleton: res.users()
```


This is because the method `is_google_calendar_synced` expected a single
record, but since we removed `user_id` from the event (appointment),
it will generate a singleton error.

This commit will fix the above issue by not calling `is_google_calendar_synced`
when the event does not have `user_id`.

sentry-7393595716

Forward-Port-Of: odoo/enterprise#113966

#appointments#google calendar#integration

[FIX] l10n_pe_edi: fixes tests

PR #114159

Enterprisesaas-18.4l10n_pe_edi

This update addresses a broken test within the l10n_pe_edi module, specifically related to unit price rounding for PEPOL compliance. The fix ensures accurate calculations for Peruvian electronic invoicing, maintaining compliance with local tax regulations. This resolves a technical issue that could have impacted invoice accuracy.

Original PR description

https://github.com/odoo/odoo/commit/e79136d04c844f9a0a8c6d0532c65e0cc3a68b8f fixes unit price rounding in peppol.
This PR fixes a broken test in l10n_pe_edi

opw-6009771

#Peru#E-Invoicing#Compliance#Tax

[FIX] (website_)sale_renting: relativedelta on time-zoned dates

PR #114086

Enterprisesaas-18.4website_sale_rentingsale_rentingMEDIUM

This update fixes an issue where rental price calculations were inconsistent due to how relativedelta handled time-zoned dates. The change ensures accurate price calculations across different time zones, specifically addressing discrepancies in rental durations. This improves the reliability of rental pricing for all users.

Original PR description

Relativedelta on UTC dates or time-zoned dates doesn't return the same result. 
In order to calculate consistent prices (price for 1 month in December = price for 1 month in January), we need to work on time-zoned dates.

Example: 
Consider a website in UTC+1 (Brussels timezone DST off).
And a rental from the 01/12/2025 to the 31/12/2025 = by design, from the 01/01/2025 00h00 (start_date) to the 31/12/2025 23h59 (end_date). 
Converted in UTC for the back-end, we have:
from the 30/11/2025 23h00 to the 31/12/2025 22h59.
relativedelta(end_date, start_date) = time between the 2 dates is calculated as follow:
30/11/2025  23h00 + 1 month = 30/12/2025 23h00 +23h59 = 31/12/2025 22h59. 
Time difference = 1 month, 23 hours, 59 minutes. 
Price = 2 months. 

Consider a second rental from the 01/01/2026 to the 31/01/2026. 
31/12/2025 23h00 + 30 days = 30/01/2026 23h + 23h59 = 31/01/2026 22h59. 
Time difference = 30 days, 23 hours, 59 minutes.
Price = 1 month. 

opw-5130762

Forward-Port-Of: odoo/enterprise#102109
Forward-Port-Of: odoo/enterprise#98571

#pricing#rental#timezone#calculation

[FIX] account_reports: prevent line breaks on negative numbers

PR #113986

Enterprisesaas-18.4account

This update resolves an issue where negative numbers in accounting reports (like customer statements) were incorrectly formatted, splitting the minus sign and amount across lines. This ensures consistent and accurate display of financial data when reports are printed, improving readability and preventing potential misinterpretations.

Original PR description

When printing accounting reports such as customer statements, a negative number may be split across two lines, leaving the minus sign on the first line and the amount on the second.

Steps to reproduce:
- Make an invoice for [Partner] with a total of 10.0
- Make another invoice for [Partner] with a total of 100.0
- Create a credit note for this last invoice
- Open the customer statement report for [Partner]
- Print PDF

Issue: The first line of the partner section has fewer digits than the amounts of the subsequent journal items. On pdf, the column width is based on the smaller line, causing the longer negative strings to wrap and separate the minus sign from the amount.

opw-5951300

Forward-Port-Of: odoo/enterprise#113727

#reporting#accounting#PDF

[FIX] l10n_cl_edi: fix missing default LATAM journal

PR #112168

Enterprisesaas-18.4l10n_cl_ediMEDIUM

This update resolves an error that occurred when processing DTE XML files from Chile. Specifically, the system was incorrectly setting a default journal, leading to a 'journal_id' error during account move calculations. This fix ensures proper DTE XML processing and prevents data discrepancies.

Original PR description

Currently, when receiving a DTE XML fetched by the fetchmail server, if there is no purchase journal with `l10n_latam_use_documents` enabled, an empty recordset (account.journal()) is set in the default context values.

This prevents the proper computation of the field and raises an error, since the `journal_id` is mandatory on account moves.

Steps to reproduce:
- Ensure you have no purchase journal with `l10n_latam_use_documents` enabled
- Simulate the reception of a DTE XML via the fetchmail server
- Observe the error: "NotNullViolation: null value in column 'journal_id'"

opw-5950116
opw-6111041

#Chile#DTE XML#Accounting

[FIX] l10n_au_hr_payroll: prevent error when employee schedule pay is not set

PR #113623

Enterprisesaas-18.4l10n_au_hr_payroll

This fix addresses a technical issue in the Australian payroll module that occurred when an employee's scheduled pay was removed. Removing this setting caused an error during wage calculation, preventing accurate payroll processing. The update corrects this logic to ensure proper wage calculations regardless of schedule pay settings.

Original PR description

This error occurs when the schedule pay is removed from an employee contract with a defined wage.

Steps to reproduce:
- Install `l10n_au_hr_payroll` module with demo data
- Switch to `My Australian Company`
- Open any Employee > Payroll > `Wage` remove `schedule pay`

Traceback:
```py
 File "/home/odoo/src/enterprise/saas-19.2/l10n_au_hr_payroll/models/hr_version.py", line 549, in _compute_wage
    version.wage = Payslip._l10n_au_convert_amount(daily_wage, "daily", version.schedule_pay)
  File "/home/odoo/src/enterprise/saas-19.2/l10n_au_hr_payroll/models/hr_payslip.py", line 511, in _l10n_au_convert_amount
    coefficient = PERIODS_PER_YEAR[period_from] / PERIODS_PER_YEAR[period_to]
KeyError: False
```

We are encountering this error because the `schedule pay` is removed, causing the field to become `False`. This False value is then passed to the `_l10n_au_convert_amount` [method], resulting in a `KeyError`.

[method]: https://github.com/odoo/enterprise/blob/92c584cc1426ac70f6f77aa8216c17004fa42d35/l10n_au_hr_payroll/models/hr_payslip.py#L500-L509

sentry-7401189447

#payroll#australia#hr

[FIX] knowledge: restore embedded views dropdown closing logic

PR #114082

Enterprisesaas-18.4knowledge

This update resolves an issue where dropdowns within knowledge articles weren't closing when clicking outside the article. The fix adjusts the way the system detects clicks, ensuring dropdowns close as expected. This improves the user experience when working with knowledge articles.

Original PR description

Steps to reproduce:
- Go to knowledge
- Type "/view" in the article -> add a list view
- Open a dropdown in that list view (e.g. the cog icon next to "New")
- Click outside the list view (e.g. first paragraph of the knowledge
  article that contains the list view)
=> The dropdown does not close

Commit [1] removed the `activeEl` param of `popoverCloseOnClickAway`, and inverted the need for the knowledge patch added at [2] (before, it was needed to be able to close dropdowns by clicking inside knowledge embedded views, it is now needed to be able to close them by clicking outside the embedded views). In 19.2, this patch could be removed entirely as [3] made a generic solution for this to work (it will probably be done once this reaches master though).

[1]: https://github.com/odoo/odoo/commit/1fb00045c6826ee7c8a7581ff4ab9b3eb2e83478
[2]: https://github.com/odoo/enterprise/commit/97c600ca35ae0513860467e572d587b977617d36
[3]: https://github.com/odoo/odoo/commit/48be3442b2b022c18d9e5d4fc8b9631563094d8e

#knowledge#dropdown#UI

Currently an error is generated when the user tries to save an appointment as follows: - Install the appointment_google_calendar module without demo data - Create a new appointment as below: - Remove Organizer (user_id) - Set the Google Meet link inside VideocallURL, e.g., https://meet.google.com/aaa-aaa-aaa - An error occurs in the log and a message is shown to the user when save the record - Also, an error occurs when trying to preview `Appointment: Attendee Invitation` after creating appointment as follows: - Set the Google Meet link inside Videocall URL > save - Remove Organizer (user_id) Error: ``` test odoo.addons.mail.models.mail_render_mixin: Failed to render QWeb template for Mail Template: 'Appointment: Appointment Booked' (ID: 12) - Context language:en_US Target Model: calendar.event Error: Error while render the template ValueError: Expected singleton: res.users() ``` This is because the method `is_google_calendar_synced` expected a single record, but since we removed `user_id` from the event (appointment), it will generate a singleton error. This commit will fix the above issue by not calling `is_google_calendar_synced` when the event does not have `user_id`. sentry-7393595716 Forward-Port-Of: odoo/enterprise#113966

Relativedelta on UTC dates or time-zoned dates doesn't return the same result. In order to calculate consistent prices (price for 1 month in December = price for 1 month in January), we need to work on time-zoned dates. Example: Consider a website in UTC+1 (Brussels timezone DST off). And a rental from the 01/12/2025 to the 31/12/2025 = by design, from the 01/01/2025 00h00 (start_date) to the 31/12/2025 23h59 (end_date). Converted in UTC for the back-end, we have: from the 30/11/2025 23h00 to the 31/12/2025 22h59. relativedelta(end_date, start_date) = time between the 2 dates is calculated as follow: 30/11/2025 23h00 + 1 month = 30/12/2025 23h00 +23h59 = 31/12/2025 22h59. Time difference = 1 month, 23 hours, 59 minutes. Price = 2 months. Consider a second rental from the 01/01/2026 to the 31/01/2026. 31/12/2025 23h00 + 30 days = 30/01/2026 23h + 23h59 = 31/01/2026 22h59. Time difference = 30 days, 23 hours, 59 minutes. Price = 1 month. opw-5130762 Forward-Port-Of: odoo/enterprise#102109 Forward-Port-Of: odoo/enterprise#98571

When printing accounting reports such as customer statements, a negative number may be split across two lines, leaving the minus sign on the first line and the amount on the second. Steps to reproduce: - Make an invoice for [Partner] with a total of 10.0 - Make another invoice for [Partner] with a total of 100.0 - Create a credit note for this last invoice - Open the customer statement report for [Partner] - Print PDF Issue: The first line of the partner section has fewer digits than the amounts of the subsequent journal items. On pdf, the column width is based on the smaller line, causing the longer negative strings to wrap and separate the minus sign from the amount. opw-5951300 Forward-Port-Of: odoo/enterprise#113727

Currently, when receiving a DTE XML fetched by the fetchmail server, if there is no purchase journal with `l10n_latam_use_documents` enabled, an empty recordset (account.journal()) is set in the default context values. This prevents the proper computation of the field and raises an error, since the `journal_id` is mandatory on account moves. Steps to reproduce: - Ensure you have no purchase journal with `l10n_latam_use_documents` enabled - Simulate the reception of a DTE XML via the fetchmail server - Observe the error: "NotNullViolation: null value in column 'journal_id'" opw-5950116 opw-6111041

This error occurs when the schedule pay is removed from an employee contract with a defined wage. Steps to reproduce: - Install `l10n_au_hr_payroll` module with demo data - Switch to `My Australian Company` - Open any Employee > Payroll > `Wage` remove `schedule pay` Traceback: ```py File "/home/odoo/src/enterprise/saas-19.2/l10n_au_hr_payroll/models/hr_version.py", line 549, in _compute_wage version.wage = Payslip._l10n_au_convert_amount(daily_wage, "daily", version.schedule_pay) File "/home/odoo/src/enterprise/saas-19.2/l10n_au_hr_payroll/models/hr_payslip.py", line 511, in _l10n_au_convert_amount coefficient = PERIODS_PER_YEAR[period_from] / PERIODS_PER_YEAR[period_to] KeyError: False ``` We are encountering this error because the `schedule pay` is removed, causing the field to become `False`. This False value is then passed to the `_l10n_au_convert_amount` [method], resulting in a `KeyError`. [method]: https://github.com/odoo/enterprise/blob/92c584cc1426ac70f6f77aa8216c17004fa42d35/l10n_au_hr_payroll/models/hr_payslip.py#L500-L509 sentry-7401189447

Steps to reproduce: - Go to knowledge - Type "/view" in the article -> add a list view - Open a dropdown in that list view (e.g. the cog icon next to "New") - Click outside the list view (e.g. first paragraph of the knowledge article that contains the list view) => The dropdown does not close Commit [1] removed the `activeEl` param of `popoverCloseOnClickAway`, and inverted the need for the knowledge patch added at [2] (before, it was needed to be able to close dropdowns by clicking inside knowledge embedded views, it is now needed to be able to close them by clicking outside the embedded views). In 19.2, this patch could be removed entirely as [3] made a generic solution for this to work (it will probably be done once this reaches master though). [1]: https://github.com/odoo/odoo/commit/1fb00045c6826ee7c8a7581ff4ab9b3eb2e83478 [2]: https://github.com/odoo/enterprise/commit/97c600ca35ae0513860467e572d587b977617d36 [3]: https://github.com/odoo/odoo/commit/48be3442b2b022c18d9e5d4fc8b9631563094d8e