Odoo Changelog — 2025-05-26

Monday, May 26, 2025

62 changes

Branch: saas-18.3

16 changes

Bug Fixes(4)

Resolved issues and error corrections

[FIX] l10n_nl_reports: in SBR report, closing entry may be None

PR #86178

Enterprisesaas-18.3l10n_nl_reports

The Dutch SBR tax report now handles cases where no closing entry exists without crashing. This keeps report generation stable after changes to the tax return process.

Original PR description

After the introduction of the new tax return process, `None` may now be returned as a closing entry, instead of an empty `recordset`. The SBR report may traceback if no closing entry is found.

#Dutch reports#SBR#tax report#stability

[FIX] l10n_fr_fec_import: Fixed unit test file reading

PR #86336

Enterprisesaas-18.3l10n_fr_fec_import

The test process for importing French FEC accounting files now reads the full file every time, avoiding occasional failures with larger files. This improves build reliability without changing user-facing functionality.

Original PR description

The JS unit test of the FEC parser was having a flaky build error because
for reading files, the test was using `.getReader().read()`
which would read only one chunk from the stream, causing incomplete files to be processed for large files.
This commit makes the unit test use `response.arrayBuffer()` instead
to guarantee the processing of the complete files all the time.

build_error-161014

#tests#reliability#FEC

[FIX] account_reports: fix submission date not visible

PR #86165

Enterprisesaas-18.3account_reports

A display issue in accounting reports was fixed so the submission date now appears as expected in the Kanban view. This helps users quickly see when returns were submitted without opening each record.

Original PR description

The submission date is never visible due to incorrect record access
in Kanban view. used `record.date_submission.raw_value`
Instead of incorrect direct usage.

#accounting#reports#kanban#submission date

[FIX] account_winbooks_import: prevent error on importing Winbooks

PR #85950

Enterprisesaas-18.3account_winbooks_import

Importing a Winbooks ZIP file with empty data files no longer causes an error. This prevents accounting users from being blocked when an export contains no partner records to import.

Original PR description

Currently, an error is produced when importing a **Winbooks** `.zip` file that contains empty `.dbf` data files. **Steps to reproduce:** - Install the `accountant`, `l10n_be` and…

Currently, an error is produced when importing a **Winbooks** `.zip` file that contains empty `.dbf` data files.

**Steps to reproduce:**
- Install the `accountant`, `l10n_be` and `account_winbooks_import` module.
- Change the default company to **BE Company CoA**.
- Navigate to accounting settings and Under **Accounting Import**  click to **import** button.
- Click **Import WBK** button and upload [this](https://drive.google.com/file/d/1wsLin2kOvlZvl0HcrzUafgRxPOVxPrcS/view?usp=sharing) file.

**Error:**
`AssertionError`

Here, an error occurs because `partner_data_dict.values()` at [1] returns an `dict_values` object, which may be empty. This value is passed directly to `ResPartner.create(...),` but the ORM method requires a list or tuple, by an assertion added at [2].

[1] - https://github.com/odoo/enterprise/blob/9d51f5171b3c2478599dde1ce991c90fa6fed32b/account_winbooks_import/wizard/import_wizard.py#L126
[2] - https://github.com/odoo/odoo/blob/6ef8565053352e4f679d26032e5485474fda62ce/odoo/orm/models.py#L4309

This commit resolves the issue when files are empty and no partner data is available for import.

Sentry - 6611894804

Other(12)

Miscellaneous changes

[FW][FIX] account_batch_payment: Fix test and payments domain

PR #86357

Enterprisesaas-18.3

* Previously, the domain only included payments in the "in_process" state, which is incorrect when only the Invoicing app is installed -paid payments should also be allowed-. * Test was failing with single app installed when accountant module was not installed. When only Invoicing, we can validate a batch payment even when payments are in paid state, so the Warning was not raised causing tests to fail. Forward-Port-Of: odoo/enterprise#86217

Original PR description

* Previously, the domain only included payments in the "in_process" state, which is incorrect when only the Invoicing app is installed -paid payments should also be allowed-.

* Test was failing with single app installed when accountant module was not installed. When only Invoicing, we can validate a batch payment even when payments are in paid state, so the Warning was not raised causing tests to fail.

Forward-Port-Of: odoo/enterprise#86217

Branch: 18.0

9 changes

Improvements(1)

Enhancements to existing features

[IMP] hr_holidays: Align leave_type display name

PR #208827

Core18.0hr_holidays

The Time Off app now shows leave type names consistently between the management form and the dashboard. This reduces confusion for users and improves the overall experience when reviewing or managing leave requests.

Original PR description

- in the management form view, the leave type display name is diffrent than dash borad one which is not the best for UX. So, remove the restriction on the display name as multiple request is handeled on its own wizard now.

Task: 4774751

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

#time-off#leave-types

Rows:Rows per page:

10 25 50 100

1 / 3Page 1 of 3 · 62 days total

The JS unit test of the FEC parser was having a flaky build error because for reading files, the test was using `.getReader().read()` which would read only one chunk from the stream, causing incomplete files to be processed for large files. This commit makes the unit test use `response.arrayBuffer()` instead to guarantee the processing of the complete files all the time. build_error-161014

Currently, an error is produced when importing a **Winbooks** `.zip` file that contains empty `.dbf` data files. **Steps to reproduce:** - Install the `accountant`, `l10n_be` and `account_winbooks_import` module. - Change the default company to **BE Company CoA**. - Navigate to accounting settings and Under **Accounting Import** click to **import** button. - Click **Import WBK** button and upload [this](https://drive.google.com/file/d/1wsLin2kOvlZvl0HcrzUafgRxPOVxPrcS/view?usp=sharing) file. **Error:** `AssertionError` Here, an error occurs because `partner_data_dict.values()` at [1] returns an `dict_values` object, which may be empty. This value is passed directly to `ResPartner.create(...),` but the ORM method requires a list or tuple, by an assertion added at [2]. [1] - https://github.com/odoo/enterprise/blob/9d51f5171b3c2478599dde1ce991c90fa6fed32b/account_winbooks_import/wizard/import_wizard.py#L126 [2] - https://github.com/odoo/odoo/blob/6ef8565053352e4f679d26032e5485474fda62ce/odoo/orm/models.py#L4309 This commit resolves the issue when files are empty and no partner data is available for import. Sentry - 6611894804

- in the management form view, the leave type display name is diffrent than dash borad one which is not the best for UX. So, remove the restriction on the display name as multiple request is handeled on its own wizard now. Task: 4774751 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

**Steps to reproduce:** - Install `sale_commission_linked_achievement` module - Enable Commissions in settings - Go to Sales > Commissions > Commissions - Group By Sales Team - Error `psycopg2.errors.UndefinedFunction: operator does not exist: text = integer` is triggered **Issue:** When generating a raw query with a untyped `NULL` value (`NULL AS team_id`) in a `WITH` subquery, PostgreSQL infers the type as `text` (instead of default `unknown`) when the clause is done. This leads to a comparison error when joining results during the `group_by` operation. `ON ("sale_commission_report"."team_id" = "sale_commission_report__team_id"."id")` Explanation in PostgreSQL source code: ``` * If all the inputs were UNKNOWN type --- ie, unknown-type literals --- * then resolve as type TEXT. This situation comes up with constructs * like SELECT (CASE WHEN foo THEN 'bar' ELSE 'baz' END); SELECT 'foo' * UNION SELECT 'bar'; It might seem desirable to leave the construct's * output type as UNKNOWN, but that really doesn't work, because we'd * probably end up needing a runtime coercion from UNKNOWN to something * else, and we usually won't have it. We need to coerce the unknown * literals while they are still literals, so a decision has to be made * now. ``` This can be reproduced manually by doing : ``` WITH example AS ( SELECT NULL AS team_id ) SELECT pg_typeof(team_id) FROM example; pg_typeof ----------- text (1 row) ``` **Fix:** Explicitly cast the `NULL` value to the proper type using `NULL::INTEGER` to ensure it is treated as an integer during the comparison. The issue was introduced here : https://github.com/odoo/enterprise/commit/80beef2077c3b4fa7ee6e20dd2f9400a7d1d2273 And, as the `sale_commission_linked_achievement` will be removed, as well as the `Sales Team` grouping, it should disappear with this : https://github.com/odoo/enterprise/commit/b1e41f9b23aa62bfd6f9be1feb1059b3507f2ce5 opw-4765421 Forward-Port-Of: odoo/enterprise#85399 Forward-Port-Of: odoo/enterprise#85097

Creating POS payment methods requires being a POS admin, which the POS user is not, and the test user may not be. Bypass issue by creating payment methods in sudo. https://runbot.odoo.com/odoo/error/222989

The adaptations from [1] and [2] added some code to the snippet preview dialog, mainly to adapt text highlights in the snippets content (starting from `18.0`) and enable the snippets preview interactions (starting from `18.3`) [A]. In a runbot test context, the snippet selection happens too fast that the code from [A] (linked to the async behaviour of `insertSnippets`) can still process the snippets dialog `iframeDocument` (lost after the dialog being closed on snippet selection). The goal of this commit is to fix this behaviour by simply taking into consideration the fact that the preview content can be lost (since in a real use case, a user will select a snippet in a reasonable time). [1]: https://github.com/odoo/odoo/commit/1aaf483c5d3b8e8816cfbea7da96ac007a42d492 [2]: https://github.com/odoo/odoo/commit/e008c92fcad2b8cc160586ba6ab94bc077b9bf3d Remark: This commit will be adapted on `18.3` to fix the code from [2]. runbot-190596

We only want to compute a journal id for a payment if: - it's a new payment (never saved). - the company changed. Backport of #199573 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

**Steps to reproduce this issue:** 1) Install Time Off 2) Create an approved leave record 3) Click on the approved leave record in month mode(calendar view) 4) The Delete button appears instead of the Cancel button **Issue:-** In the Time off dashboard, in the year view, if I click on a leave and open the popup, I can click on “Cancel” to cancel my leave But this “Cancel” button appears as “Delete” in the month, week and day views. However, it does cancel the leave, not delete it. **Solution:-** This button should be renamed “Cancel” to be consistent with the system. opw-4782277

Problem: When in dark mode, additional styles are applied to improve display. However, these styles are inadvertently preserved during `convert_inline`, which processes HTML for email rendering. This causes unwanted dark mode styles (e.g., `background-color`, `border-color`, and `color`) to persist even after switching back to light mode, especially in email signatures. Solution: Skip stylesheets that only affect `color`, `background-color`, or `border-color` on `table` elements. This avoids incorrect rendering in light mode without removing essential formatting styles. Note: Skipping all styles caused layout issues, so the fix targets only problematic styles. Fixed in `web_editor`: https://github.com/odoo/odoo/commit/d076dbcc273be5c8f337de9263effa82c9d9c0c8 Steps to reproduce: 1. Switch to dark mode. 2. Add an email signature in user preferences. 3. Switch back to light mode. 4. Open the mail composer. → The signature table shows a dark background. 5. Send the email. → The table in the mail thread still has a dark background. opw-4713718 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Currently, an error occurs when sorting is applied again on a different related field after sorting another related field first. Steps to reproduce: - Install `accountant` module - Navigate `Accounting > Accounting > Assets (list view)` - Apply Sorting on column `Fixed Asset Account` - Try to sort the column `Depreciation Account` - Observe the error Error: `AssertionError` The issue occurs when attempting to add a JOIN on an SQL query without verifying whether it has already been included. - [1] This commit resolves the issue by adding a conditional check before adding a join in the query, ensuring that duplicate joins are not added. [1] - https://github.com/odoo/odoo/blob/b2e564f07f6883111da4581bccfb0f45c7588063/addons/account/models/account_account.py#L150-L152 Sentry-6039417751

Branch: saas-18.3

Bug Fixes(4)

[FIX] l10n_nl_reports: in SBR report, closing entry may be None

[FIX] l10n_fr_fec_import: Fixed unit test file reading

[FIX] account_reports: fix submission date not visible

[FIX] account_winbooks_import: prevent error on importing Winbooks

Other(12)

[FW][FIX] account_batch_payment: Fix test and payments domain

Branch: 18.0

Improvements(1)

[IMP] hr_holidays: Align leave_type display name

Branch: saas-18.3

Bug Fixes(4)

[FIX] l10n_nl_reports: in SBR report, closing entry may be None

[FIX] l10n_fr_fec_import: Fixed unit test file reading

[FIX] account_reports: fix submission date not visible

[FIX] account_winbooks_import: prevent error on importing Winbooks

Other(12)

[FW][FIX] account_batch_payment: Fix test and payments domain

Branch: 18.0

Improvements(1)

[IMP] hr_holidays: Align leave_type display name

[FW][FIX] l10n_mx_edi_website_sale: ensure test data is set up

[FW][FIX] delivery_{ups_rest, sendcloud}: let Amazon get the expected carrier's type

[FW][FIX] mail_enterprise: livechat visitor counter badge is red

[FW][I18N] l10n_cz_reports{_2025}: update translations

[FW][FIX] sale_commission_linked_achievement: cast NULL type in raw query

[FW][FIX] documents: correctly display search panel

[FW][FIX] voip: send keep-alives to avoid silent disconnection

[FW][FIX] account_batch_payment: some batch payment fixes

[FW][IMP] l10n_uk_reports: send module version

[FW][IMP] l10n_eu_oss_reports: Ensure the product OSS tag on accounting i…

[FW][FIX] website_sale_renting: website_sale_renting_select_wrong_period

Bug Fixes(6)

[FIX] l10n_test_pos_qr_payment: test setup ACLs

[FIX] web_editor: fix the snippets preview dialog testing behaviour

[FIX] account: payment compute journal id

[FIX] hr_holidays: give correct label to delete button based on the leave state

[FIX] mail: skip dark mode styles in email signature rendering

[FIX] account: prevent error when applying sorting on assets list

Refactoring(1)

[REF] web_tour: Improving understanding of indeterminisms

Other(1)

[FW][FIX] website: popup with scrollbar doesn't scroll