Odoo Changelog — 2025-05-26

Monday, May 26, 2025

38 changes · saas-18.3

Bug Fixes(5)

Resolved issues and error corrections

[FIX] crm: crm_tour: remove delay

Coresaas-18.3crm

This update removes an outdated waiting period from an automated CRM walkthrough. It helps internal validation run more smoothly now that modal windows close reliably, with no expected change for everyday users.

Original PR description

Since [1], we now wait ´onClose´ before closing modals and this delay is not necessary anymore.

Before [1], the tour clicked on a kanban record that should have opened a form view but that was cancelled by the ´switchView()´ because a modal was detected.
The issue was that modal was closed too soon leaving the tour clicking on the kanban card while the instance of modal is still alive even if not in the DOM anymore.

Now that modal closing is synchronized, we can safely remove this delay without any risk of being blocked by the ´switchView()´ because of a modal residue.

[1] https://github.com/odoo/odoo/pull/210521

runbot-error: 181875

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

#crm#testing#automation

[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(33)

Miscellaneous changes

[FW][FIX] account: reports: properly rename tax tags instead of creating them when modifying an expression's formula

PR #211646

Coresaas-18.3account

When writing a new formula on a tax_tags expression, but also providing the 'engine' key with 'tax_tags' value, this condition https://github.com/odoo/odoo/blob/16.0/addons/account/models/account_report.py#L539 triggered and the return at the end of it caused the tag to be recreated instead of renamed. This case can happen when changing the name of a tag in a data file, then updating the module. We saw it while working on an cleaned version of a localized report for master. Forward-Port-Of:

Original PR description

When writing a new formula on a tax_tags expression, but also providing the 'engine' key with 'tax_tags' value, this condition https://github.com/odoo/odoo/blob/16.0/addons/account/models/account_report.py#L539 triggered and the return at the end of it caused the tag to be recreated instead of renamed.

This case can happen when changing the name of a tag in a data file, then updating the module. We saw it while working on an cleaned version of a localized report for master.

Forward-Port-Of: odoo/odoo#211408
Forward-Port-Of: odoo/odoo#210811

Since [1], we now wait ´onClose´ before closing modals and this delay is not necessary anymore. Before [1], the tour clicked on a kanban record that should have opened a form view but that was cancelled by the ´switchView()´ because a modal was detected. The issue was that modal was closed too soon leaving the tour clicking on the kanban card while the instance of modal is still alive even if not in the DOM anymore. Now that modal closing is synchronized, we can safely remove this delay without any risk of being blocked by the ´switchView()´ because of a modal residue. [1] https://github.com/odoo/odoo/pull/210521 runbot-error: 181875 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

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

Message bubble color in dark theme were too light grey, which make text hard to read. Also the greyish tint makes discuss look sad. White theme color are not much saturated, but the light background makes it good enough in comparison. This commit fixes the issue by darkening and adding more saturation to message bubble in dark theme. This gives them a more mature look with text more readable. This commit makes similar improvement to important messaging menu items in dark theme. White theme color has been slightly improved with a bit more color saturation on message bubble and notification item bg. This PR also makes these other notable changes: - shadow effects (message bubble, inputs, badges, etc.) - message actions are horizontally more compact - starred messages have starred icon in their sidebar - useHover away timing is reduced to 100ms (down from 200ms), so that this feels snappier. - chat bubble in mobile don't have close button: was too prone for accidental click with thumb - thread banners have new style with floating rounded alerts - chat window unread counter is next to name rather than always next to chat window quick actions. - message bubbles in mobile do not go in the turf of bubbles in opposite alignment (i.e. more spacing at their end). Should make it easier to read conversation in mobile. Forward-Port-Of: odoo/odoo#211362

**Problem:** For products with variants and differents steps for the BoM depending on the variant, the Manufacturing Order overview for a given product with a given variant would display the sum of the cost of all variants possible for this product. If we had a product "Drawer" with a color variant "Black" and "White", which cost 10 and 20 euros respectively, the Manufacturing Order overview of a Black Drawer would display the cost of the drawer + **30** euros (10+20), instead of being the cost of the drawer + **10** euros. The display cost is the sum of the price of every variants for this product, instead of being the price of the current variant of the product. **Steps to reproduce:** - Create a product with variants - Change the BoM and make some components needed only for certain variants and add a price for them - Go to the MO overview - The Cost BoM cost total is the sum of all prices AND variants **Cause of the issue:** https://github.com/odoo/odoo/blob/d3ab7b2c3ceddbb4cb8d8e91fac0d60e28e5673a/addons/mrp/report/mrp_report_mo_overview.py#L85 This treats every remaining lines of the BoM as a missing component, thus adding it's price to the total price. Some lines should only be applied if a specific variant is selected, but with this code, every line that has a condition depending on variants will be taken in. **Fix:** Before adding the product of a BoM line to the missing components, we check that the BoM line should be applied to the current variant. The missing components are still used and can be not empty in the case where the BoM includes a line that was deleted from the MO, making the MO cost and the BoM cost different. In this case, the missing components will not be empty and will still work as intended without taking the unwanted variants into account. opw-4557169 Forward-Port-Of: odoo/odoo#199264

**Problem:** when doing a refund from pos of an avco (or fifo) product, with the option "ship later" the cost of the product does not appear on the pos order line **Steps to reproduce:** - Enable Settings "Allow Ship Later", "Automatic Accounting" - Navigate to Sales/Configuration/Product Categories - Create a new category with Inventory Valuation field as "Automated" and the Costing Method field as "Average Cost (AVCO)" - Open Point of Sale/Product - Create a new storable product - In the general information tab set a cost and select your new category for the product category field - In the Sales tab, make sure that "Available in POS" is checked and select a category - Set an on Hand quantity - Open a point of sale from the Point of Sale Dashboard - Select your product and click on Payment - On the top right of the screen select a customer with an adress, click on Invoice and on Ship later - Select a payment method and validate - Navigate to Point of Sale/Orders - click on the last order created, and click on the "Pickings" smart button - validate the picking - come back to the store in point of sale - select the three horizontal lines on the top right and click on Orders - filter by paid orders - select the last order created and click on refund and then on payment - check Invoice and Ship Later on the top right, select a payment method and validate - Navigate back to Point of Sale/orders and select the last order created **Current behavior:** The total cost is zero on the pos order line Even if the delivery is validated via the Picking smart button the total cost is still zero **Expected behavior:** It should reflect the cost of the product (depending on the costing method) **Cause of the issue:** When the pos order is created from Point of Sale, the process_saved_order method is called this method calls (1)create_order_picking and then (2)compute_total_cost. https://github.com/odoo/odoo/blob/504ef7cdeb1600b86feefbe8668144da9cd5a70b/addons/point_of_sale/models/pos_order.py#L183-L184 **Scenario A** Inside (1) create_order_picking, if the PosOrder doesn't have a shipping_date the if statement is False https://github.com/odoo/odoo/blob/504ef7cdeb1600b86feefbe8668144da9cd5a70b/addons/point_of_sale/models/pos_order.py#L1017 and the method _create_picking_from_pos_order_lines is called. This method then calls _action_done. https://github.com/odoo/odoo/blob/504ef7cdeb1600b86feefbe8668144da9cd5a70b/addons/point_of_sale/models/stock_picking.py#L70 Inside the stock_account override of _action_done, _create_in_svl is called. https://github.com/odoo/odoo/blob/504ef7cdeb1600b86feefbe8668144da9cd5a70b/addons/stock_account/models/stock_move.py#L289 This method sets the value of the stock_valuation_layer_ids attribute of the stock move to a new stock valuation layer. **Scenario B** Inside (1) create_order_picking, if the PosOrder has a shipping_date (in the case where we selected "Ship Later") the method _launch_stock_rule_from_pos_order_lines is called. https://github.com/odoo/odoo/blob/504ef7cdeb1600b86feefbe8668144da9cd5a70b/addons/point_of_sale/models/pos_order.py#L1017-L1018 and nowhere inside this method is _action_done called. This makes sense because the stock move hasn't been validated. When (2) compute_total_cost is then called by process_saved_oder, if the product category is avco, _compute_average_price will be called. If we are in Scenario B there is no stock valuation layer for this stock move. Consequently there will be no candidates and the price will not be computed. https://github.com/odoo/odoo/blob/504ef7cdeb1600b86feefbe8668144da9cd5a70b/addons/stock_account/models/product.py#L795-L798 opw-4614503 Forward-Port-Of: odoo/odoo#210868 Forward-Port-Of: odoo/odoo#207482

**Steps to reproduce**: 1. Install the website_event app 2. Enable Online Exhibitors in settings 3. Open any upcoming event and check website submenu and showcase exhibitors 4. Click on the sponsor smart button 5. Create a new sponsor with type 'Exhibitor' 6. Now click on Go to website smart button and make it publish 7. Open private window in browser and go to exhibitor page by cliking on 8. Go to Event > Modified upcoming event > exhibitors submenu 9. Now click on more info button inside the exhibitor card 10. Observe the console error or Error if Debug mode is on. **Issue**: - The dialog displayed for non-event managers attempts to use t-options within a <span> tag, causing Unknown QWeb directive error. - Missing prop error in Debug mode **Solution**: - Replace the t-options logic with a dedicated property of the object with correct format of date_begin field - Add close prop in ExhibitorConnectClosedDialog **UI Improvement:** - notice on the next exhibitor page we're displaying: ```<span>(<t t-if="website_visitor_timezone != sponsor.event_id.date_tz" t-out="event.date_tz"/>)</span>``` It would be nice to remove the parentheses when the condition doesn't pass, as it currently results in empty brackets () being shown opw-4737183 Forward-Port-Of: odoo/odoo#209866

**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

Bug Fixes(5)

[FIX] crm: crm_tour: remove delay

[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(33)

[FW][FIX] account: reports: properly rename tax tags instead of creating them when modifying an expression's formula

Bug Fixes(5)

[FIX] crm: crm_tour: remove delay

[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(33)

[FW][FIX] account: reports: properly rename tax tags instead of creating them when modifying an expression's formula

[FW][FIX] point_of_sale, pos_restaurant: disable paid order editing

[FW][FIX] l10n_test_pos_qr_payment: test setup ACLs

[FW][FIX] website_event_exhibitor: sponsor link work with multi domain

[FW][FIX] mail: message bubble color in dark theme more readable

[FW][I18N] l10n_cz: update translations

[FW][IMP] certificate, l10n_es_edi_*: Factor patched HTTPAdapter for certificates models

[FW][FIX] mrp: display correct cost of manufacturing order

[FW][FIX] html_editor: applied custom color lost after switching tab

[FW][FIX] web: list: recompute column widths when width changes

[FW][FIX] point_of_sale: compute cost of delayed shipped refund avco/fifo

[FW][FIX] im_livechat: fix tour history back and forth

[FW][IMP] account: Add tracking to payments' state

[FW][PERF] stock: optimize _compute_rules

[FW][FIX] web_editor, website: prevent snippet tabs nav items removal

[FW][FIX] account: Propagate product tags on tax lines

[FW][FIX] google_address_autocomplete: fix runbot error 181592

[FW][FIX] website_event_exhibitor: unknown qweb directive error on exhibitor more info button

[FW][IMP] l10n_in_ewaybill_irn: print irn number on e-waybill report

[FW][IMP] l10n_be:Changes in the CoA (payable/receivable).

[FW][FIX] mail: close tab with call does not jump to other tab

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

[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