Odoo Changelog — 2025-03-18

Tuesday, March 18, 2025

58 changes · saas-18.2

Bug Fixes(3)

Resolved issues and error corrections

[FIX] mail: correct position of chat bubble counter and IM status

PR #202339

Coresaas-18.2mail

This fixes the placement of message counters and online status indicators on chat bubbles after recent visual updates. Users will see a cleaner, more polished chat interface with badges and status markers positioned where expected.

Original PR description

Follow-up of #201984

PR above made many style improvements, one of which was the chat bubble message preview that is closer to chat bubble. The solution of PR required reducing horizontal size of chat bubbles, therefore floating elements like counter and im_status need to be compensated.

This was done correctly for close, but IM status and counter were wrong. They should be offset by 5px, which was missing on IM status. On counter, the compensated value was done in the wrong direction... Hence the double correction.

Before / After
![Screenshot 2025-03-18 at 15 09 34](https://github.com/user-attachments/assets/c501d8a4-6683-4f8b-8932-369282bdd3b4) ![Screenshot 2025-03-18 at 15 09 15](https://github.com/user-attachments/assets/b4839728-6864-4b10-847c-e55c86dbb370)

#chat#user interface#visual fix

[FIX] mail: discuss sidebar IM status no cut on Firefox

PR #202326

Coresaas-18.2mail

This fixes a small visual issue in Discuss where online status indicators could be slightly cut off in Firefox. The sidebar items get a tiny bit more vertical spacing so user availability badges display cleanly across browsers.

Original PR description

Follow-up of https://github.com/odoo/odoo/pull/201984

PR above made a few style improvements in discuss sidebar, such as increasing the size of avatars and IM status to match the channel member list.

Since the avatars are bigger and therefore are close to border, there's a 1px vertical margin to prevent cutting IM status. However this works in chromium-based browsers but not Firefox: the position of IM status is slightly off by 1 pixel vertically for some reasons, which makes the IM status cut slightly on the bottom.

This commit fixes the issue by increasing vertical margin from 1px to 2px. This increases a bit the size of each item as a result, but thankfully it's minor drawback compared to cut IM status on Firefox.

Before / After
![Screenshot 2025-03-18 at 14 43 54](https://github.com/user-attachments/assets/997d7858-fa53-45d8-8e40-5c14b9e43788) ![Screenshot 2025-03-18 at 14 43 37](https://github.com/user-attachments/assets/3cf6df08-ab7f-4a75-b46e-7ad6b9b9e2d9)

#discuss#sidebar#firefox#visual-fix

[FIX] website_sale_collect: remove override and fix zipcode type

PR #202224

Coresaas-18.2website_sale_collect

This fixes an issue in the store pickup checkout flow that could cause errors during validation in debug mode. It also ensures missing zip codes are handled safely, helping the pickup option work more reliably for customers.

Original PR description

Props validation in debug mode failed as they were removed in
fw commit https://github.com/odoo/odoo/commit/d940fa55c465afa11fa443745f8f5a0081c8cfe3.
Fallback to an empty string for zipcode as it is expected in the
widget.

#checkout#store-pickup#zipcode

Other(55)

Miscellaneous changes

[FW][FIX] spreadsheet: fetch currency display name

PR #202341

Coresaas-18.2spreadsheet

Steps to reproduce: - Go to Accounting > Customers > Invoices - Insert the list into a spreadsheet - in any cell, type `=ODOO.LIST(1,1,"company_currency_id")` => the currency is not displayed. The reason is that the `company_currency_id` is fetched as part of a monetary field. When the new `=ODOO.LIST(1,1,"company_currency_id")` is typed, the list data source thinks it has the data, but actually the `dislay_name` is missing. Task: 4633078 --- I confirm I have signed the CLA and

Original PR description

Steps to reproduce:

- Go to Accounting > Customers > Invoices
- Insert the list into a spreadsheet
- in any cell, type `=ODOO.LIST(1,1,"company_currency_id")`

=> the currency is not displayed.

The reason is that the `company_currency_id` is fetched as part of a monetary field. When the new `=ODOO.LIST(1,1,"company_currency_id")` is typed, the list data source thinks it has the data, but actually the `dislay_name` is missing.

Task: 4633078

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

Forward-Port-Of: odoo/odoo#200886
Forward-Port-Of: odoo/odoo#200663

Follow-up of #201984 PR above made many style improvements, one of which was the chat bubble message preview that is closer to chat bubble. The solution of PR required reducing horizontal size of chat bubbles, therefore floating elements like counter and im_status need to be compensated. This was done correctly for close, but IM status and counter were wrong. They should be offset by 5px, which was missing on IM status. On counter, the compensated value was done in the wrong direction... Hence the double correction. Before / After ![Screenshot 2025-03-18 at 15 09 34](https://github.com/user-attachments/assets/c501d8a4-6683-4f8b-8932-369282bdd3b4) ![Screenshot 2025-03-18 at 15 09 15](https://github.com/user-attachments/assets/b4839728-6864-4b10-847c-e55c86dbb370)

Follow-up of https://github.com/odoo/odoo/pull/201984 PR above made a few style improvements in discuss sidebar, such as increasing the size of avatars and IM status to match the channel member list. Since the avatars are bigger and therefore are close to border, there's a 1px vertical margin to prevent cutting IM status. However this works in chromium-based browsers but not Firefox: the position of IM status is slightly off by 1 pixel vertically for some reasons, which makes the IM status cut slightly on the bottom. This commit fixes the issue by increasing vertical margin from 1px to 2px. This increases a bit the size of each item as a result, but thankfully it's minor drawback compared to cut IM status on Firefox. Before / After ![Screenshot 2025-03-18 at 14 43 54](https://github.com/user-attachments/assets/997d7858-fa53-45d8-8e40-5c14b9e43788) ![Screenshot 2025-03-18 at 14 43 37](https://github.com/user-attachments/assets/3cf6df08-ab7f-4a75-b46e-7ad6b9b9e2d9)

Props validation in debug mode failed as they were removed in fw commit https://github.com/odoo/odoo/commit/d940fa55c465afa11fa443745f8f5a0081c8cfe3. Fallback to an empty string for zipcode as it is expected in the widget.

Problem: The delivered and received quantities on sale order and purchase order lines don’t get updated during intercompany transactions for kit products. This is because the transit location is used instead of the supplier and customer locations. Purpose: Updating the filter to include transit locations will allow stock moves to and from the transit locations to be included in the delivered and received quantities. Steps to Reproduce on Runbot: 1. Enable Inter-Company Transactions for both companies, with Generate Sales Orders, Generate Purchase Orders, and Synchronize Deliveries to your Receipts selected. 2. Create a product and create a kit type bill of materials for it. Remove the company from the bill of materials so it is available for both companies. 3. Create a sale order for this kit product with the customer set to another one of your companies. 4. Confirm the sale order and validate the picking. 5. Observe the delivered quantity on the sale order line is still 0. 6. Switch to the company you sold the kit to. 7. Navigate to the purchase order that was created and confirm it. 8. Validate the picking. 9. Observe the received quantity is still 0. opw-4536144 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#199819

## Summary 1. `--test-tags ".test_js[mail > widgets]"` will start all test_js starting with "mail > widgets" 2. `--test-tags "/web,-.test_js[Components > CheckBox]"` will start all web test, but skip Components > CheckBox qunit 3. ` --test-tags ".test_js[utils,-utils > Hooks,-utils > Patch]"` start all test_js utils tests except the Hooks and Patch ones 4. `--test-tags "-.test_js[Components > CheckBox]"` will start **all** tests, but skip Components > CheckBox qunit ## Motivation Tags are used by runbot to *disable* randomly failing tests without the need to commit changes. They can precisely target a python test method, class or module. They can also be used by developer to run a *specific* test. The problem is that the qunit is a special case, a js test suite inside the test_suite. It is only possible to disable all of them, or none of them. Adding the possibility to enable/disable some of them was requested for a long time. ## Using test tags The solution to use test-tags as multiple pros: - avoid a new command line argument - runbot already manages test-tags for errors meaning that this solution would imply minimal changes on this side - passing arguments to a specific tests, without regard of the qunit needs looks like a decent solution. This is a generic solution that could lead to other posibilities (profiling, test mode, ...) Test tags are not aware of the purpose of the parameters, they will only be passed to the test. The tests has the responsibility to parse them. ## Chosen syntax and behavior The main need is to be enable/disable some qunit. This means that we may want to support having parameters using comma `,` Unfortunately this may conflict with comma used to split tags if the syntax is not well defined. The main idea to solve this issue was that it would be intuitive to give parameters as a function call would, between parentheses. The opening and closing of the parentheses would allow to identify if a comma is part of the parameters or a tag separator. But using parenthesis is not a good idea in a command line since it could be interpreted by the shell. The chosen alternative was to use `[]` to have a opening and closing symbol. Depending on how the parameters are interpreted, it can also be quite intuitive to understand: we select a specific element. `.test_js[mail,stock]` to run only js tests concerning mail and stock. The idea to disable some qunit would be to specify a negative filter as for tags: `.test_js[-some_module]` Multiple matching tags may be given, in this case all parameters are given to the test. This is why test_parameters are a list of strings. `.test_js[-m1,-m2],.test_js[-m3]` will be given to the test as `['-m1,-m2', '-m3']` ## Splitting the tags The idea to support nested [] in params was considered but this would complexify a lot the parsing `.test_method[filters=[mail,crm],failfast=0]` This is NOT supported even if it could be. Parsing such tags would need a more complex parser (to split the , ) The final decision was made to keep it simple for now since it wouldn't be a problem to add this in the future if needed. ## Negating a parametric tag A test tag can be negated to disable a test `-.test_js` (no op if test_js was not expected to run) The question is, what is the expected behaviour of `-.test_js[mail]`. ### 1. Forbid this form Simple solution, consider it as disabling a test, so passing the parameters would be usellesss and we should just don't allow that. But forbidding this form may force to make some complex development in runbot, since the current logic to disable a test is to add a '-' in front of the tag extected to run the test. ### 2. Transform it to negate the parameter It could be as simple as transforming `-.test_js[mail]` to `.test_js[-(mail)]`, or to manage the case when we could have already negated arguments (and multiple ones), tansform it to `.test_js[-mail-]` The only cons of this solution is that adding the tag -.test_js[mail] would actually enable the test_js even if it is not the case, and be more equivalent to `.test_js,.test_js[-mail]` ### 3. Consider them apart: negated but not including. With this last solution, it is not possible to translate it as a tag, it would mean `.test_js[-mail]` if test_js is already enabled. This is whats looks to be the most robust solution. Adding a negated test-tag should not enable a test that wouldn't if not present ### 4. Always considered as parameters `.test_js[mail]` would not enable test_js, but pass mail as parameter to test_js if another test enables it. This means that to start the mail js test, we would use --test-tags .test_js,.test_js[mail] This could make sence but would be less practical. Since the main goal is to be able to disable a specific qunit from the runbot, 2, 3 and 4 could work in most cases but 2 could be problematic in edge cases, and for odoosh were we may want to use autotags but only enable test from one module. /my_module,.test_js[-some_test] would enable the test_js. 3 and 4 are equivalent for negation, but the automatic generation of config wouldn't work with 4. The current chosen solution is 3 since it looks to be the more practical. Forward-Port-Of: odoo/odoo#201474 Forward-Port-Of: odoo/odoo#200413

### Commit 1 In the point of sale environnement we want to be able to edit html field in a minimal way. So only core plugins are added to the html_editor. As we have a special assets environnement for the point_of_sale we can directly patch the main `htmlField` definition without impacting main assets of Odoo. So in Order to make it work we need to remove the preventDefault on backspace key at the initialization of PoS. Enterprise: 79703 ### Commit 2 The html editor should only work with the “CORE_PLUGINS” plugin set. But when an HTML field is used only with this Set a traceback is raised because the “MediaPlugin” plugin is missing. This is due to this piece of code: ```js async getEditorContent() { await this.editor.shared.media.savePendingImages(); return this.editor.getElContent(); } ``` Each time an HTML input is unfocused, this method is called and attempts to save the pending images. The problem is that media.savePendingImages depends on the “MediaPlugin”. A quick fix is made in this commit by adding a question mark after media to avoid traceback if the plugin is missing. Forward-Port-Of: odoo/odoo#198701 Forward-Port-Of: odoo/odoo#198482

There are currently 2 issues with the "Gaps in the sequence" warning on journals in the accounting dashboard. (1) Sequence check per company issue: We query and thus do the the sequence check only on the moves of a single company. This e.g. fails though in the following case (all moves in the same journal) ``` move0: company_A move1: company_B move2: company_A ``` The query for company_A will find a gap between move0 and move2. But there is no gap (it just belongs to a different company). (2) Lockdate per company issue: Consider the case that the child company is already locked but the parent is not. E.g ``` move0: parent company move1: child company (move is locked) move2: parent company ``` We would find a gap for the parent company. The "right" lock date to use for a journal is the lock date of the journal company: * A branch company is locked when the parent is locked. * Parent companies of the journal company can not add moves to the journal. So we will find all holes that can still be corrected. After this commit we query per lock date (instead of per company). In each query we check all the journals restricted by the same lock date. This solves both issues: (1) is solved since query all moves independent of the company (2) is not an issue since we use the "right" lock date (see reasoning above) opw-4548453 Forward-Port-Of: odoo/odoo#202124 Forward-Port-Of: odoo/odoo#201732

**Steps to reproduce:** - Install Accounting and l10n_it_edi_withholding - Switch to an Italian company (e.g. IT Company) - Import an electronic Italian invoice (XML) containing an element like: ```xml <DettaglioLinee> <NumeroLinea>2</NumeroLinea> <Descrizione>Contributo ENASARCO</Descrizione> <PrezzoUnitario>0.00</PrezzoUnitario> <PrezzoTotale>0.00</PrezzoTotale> <AliquotaIVA>22.00</AliquotaIVA> <AltriDatiGestionali> <TipoDato>CASSA-PREV</TipoDato> <RiferimentoTesto>TC07 - ENASARCO</RiferimentoTesto> <RiferimentoNumero>10.03</RiferimentoNumero> </AltriDatiGestionali> </DettaglioLinee> ``` **Issue:** 1) When the above ENASARCO element is present and its unit price is 0, we consider that the ENASARCO tax should be applied to each line. We try to retrieve the percentage of the ENASARCO tax used by computing it from the amount from <RiferimentoNumero> element and the untaxed amount of the invoice. Then the ENASARCO tax is applied on all the current move lines. However, it is possible that all the move lines have not been imported yet and the tax will not be applied on all the lines. 2) If a ENASARCO tax has been set on a particular move line with a unit price of 0, the tax is applied to all the move lines, but it shouldn't. 3) When a global ENASARCO element is found in a move line, this move line is deleted, which can cause an error if the ENASARCO tax cannot be found in the database because a message is logged with the move line name. **Solution:** 1-2. In "_l10n_it_edi_import_line" method, we had the ENASARCO tax to the current line by computing the tax rate with the unit price of the line if it is not 0. Then, in "_l10n_it_edi_import_invoice" method, we parse the XML to check if there was a unique ENASARCO element with an amount and without unit price. If it is the case, we considered the ENASARCO tax as global. Instead of using the untaxed amount of the invoice to compute the rate of the ENASARCO tax used, we should be able to retrieve the real taxable amount in a <DatiRiepilogo> element. There should be an element like: ```xml <DatiRiepilogo> <AliquotaIVA>22.00</AliquotaIVA> <ImponibileImporto>117.97</ImponibileImporto> <Imposta>25.95</Imposta> <EsigibilitaIVA>I</EsigibilitaIVA> </DatiRiepilogo> ``` from which we sum all the "ImponibileImporto" values. 3) Only remove the line if the ENASARCO tax is global and can be found in the database. Ref old fix: https://github.com/odoo/odoo/pull/197456 Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4555966) opw-4555966 Forward-Port-Of: odoo/odoo#202044 Forward-Port-Of: odoo/odoo#200774

**Steps to reproduce:** (To reproduce the issue, we have to simulate a case where "E-Factura Status" is "Sent". This can be done by editing "account_move_form_inherit_l10n_ro_edi" view and setting "l10n_ro_edi_state" field visible and editable.) - Install Accounting and l10n_ro_edi - Switch to a Romanian company (e.g. RO Company) - Create an invoice - Set "E-Factura Status" to "Sent" - Confirm it - Try to send the invoice **Issue:** 1) A traceback is raised when trying to generate the extra EDI checkbox for the "Print & Send" wizard. 2) Once the first issue fixed, the "Send E-Factura to SPV" option will be displayed in the "Print & Send" wizard with a warning tooltip button. The tooltip button will be displayed on another line, which misaligns the "Send E-Factura to SPV" option with the other ones. **Cause:** This specific code: ```py return [checkbox_key for checkbox_key, checkbox_vals in json_checkboxes.items() if checkbox_vals['checked']] ``` fails because there is no key associated to the data dict for the Romanian EDI checkbox. opw-4630524 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#201756

**Steps to reproduce** - Install PoS, and select a Mexican company - Create an order O1, and in the payment screen, select "Invoice" and confirm the dialog - Validate the order - Click on "Orders" and set the filter to "Paid" to see order O1 - Click O1, click "Refund", and from the product screen, click "Payment" Observed behavior: White screen with traceback in the console. **Issue** It's happening because in l10n_mx_edi_pos, an invoiced order is supposed to have fields `l10n_mx_edi_cfdi_to_public` and `l10n_mx_edi_usage` https://github.com/odoo/enterprise/blob/a0a97f2c87f76ae035394a67b09d71ec8f4567e7/l10n_mx_edi_pos/static/src/app/screens/payment_screen/payment_screen.js#L18-L21 And they are being accessed in the `product_screen.xml` https://github.com/odoo/enterprise/blob/0396d4f0ac33640dc042bb97e9e8d4b498e6a128/l10n_mx_edi_pos/static/src/app/screens/payment_screen/payment_screen.xml#L7-L12 That works for the original ordre (aka O1), however, when the refund order is created, we set its `to_invoice` to `true` if the original order is invoiced ([code](https://github.com/odoo/odoo/blob/53e7c0adf093dc950a42989a56b4594f734c17b2/addons/point_of_sale/static/src/app/screens/payment_screen/payment_screen.js#L69-L75)), but we don't set any values to the fields `l10n_mx_edi_cfdi_to_public` and `l10n_mx_edi_usage`, causing the crash in the payment screen. **Fix** If the refund order is invoiced, we set the `l10n_mx_edi_usage` to "G02" which corresponds to 'Returns, discounts or bonuses' (assuming that a refund can be seen as a 'return' here). We also copy the field `l10n_mx_edi_cfdi_to_public` from the original order. opw-4608630 Forward-Port-Of: odoo/enterprise#80664

Bug Fixes(3)

[FIX] mail: correct position of chat bubble counter and IM status

[FIX] mail: discuss sidebar IM status no cut on Firefox

[FIX] website_sale_collect: remove override and fix zipcode type

Other(55)

[FW][FIX] spreadsheet: fetch currency display name

Bug Fixes(3)

[FIX] mail: correct position of chat bubble counter and IM status

[FIX] mail: discuss sidebar IM status no cut on Firefox

[FIX] website_sale_collect: remove override and fix zipcode type

Other(55)

[FW][FIX] spreadsheet: fetch currency display name

[FW][FIX] purchase_mrp, sale_mrp: inter company delivered and received qty for kit

[FW][ADD] payment_nuvei: Add Nuvei payment provider integration

[FW][FIX] web: access error on dialog form view

[FW][FIX] delivery: estimated delivery cost on SO line not rounded

[FW][FIX] l10n_es: wrong sign tax tag grid for 4% G sale tax

[FW][IMP] tests: allow to run/disable specific js tests

[FW][FIX] mail: hide isTalking when self-deafened

[FW][IMP] pos_restaurant_appointment: Add minimal html editor in pos mode

[FW][FIX] website_sale_loyalty: fix expired reward test

[FW][FIX] l10n_es_edi_sii: replace expired certificate

[FW][FIX] base_automation: multiple records computation

[FW][IMP] hw_posbox_homepage: connecting loading state

[FW][FIX] point_of_sale: use localhost for proxy display

[FW][FIX] mrp_account: post labor entry once

[FW][FIX] account: fix gap in sequence warning for branches

[FW][FIX] website_sale: fix overlapping divs on mobile

[FW][REF] barcodes: convert unit tests to hoot

[FW][FIX] portal_rating: correct message reaction placement on websites

[FW][FIX] google_account, google_calendar: use google_account for calendar sync

[FW][IMP] l10n_vn_edi_viettel: Optional customer info

[FW][IMP] point_of_sale : simplify reload product text

[FW][FIX] html_editor: apply opacity for custom background colors

[FW][FIX] web: avoid reloading the view we are leaving.

[FW][FIX] sale: sudo check invoices on cancel

[FW][FIX] mrp: assign production_id to smls with no reservation

[FW][FIX] website: allow to edit menu groups

[FW][FIX] base,product: synchronization of company_dependent commercial f…

[FW][FIX] l10n_it_edi_withholding: fix edi import with enasarco lines

[FW][FIX] account: timesheet & account users cannot read analytic line

[FW][FIX] website_sale: no access to reactions for public users in ecommerce

[FW][FIX] l10n_ro_edi: fix EDI checkbox in send wizard

[FW][FIX] l10n_in_ewaybill_stock: invisible field error

[FW][FIX] l10n_in_ewaybill: correct the wrongly placed comment

[FW][FIX] account: prevent error when removing accounting date from invoice bill

[FW][FIX] mail: fix traceback when the user click schedule next without due date

[FW][FIX] html_editor: banner icon and div base container misaligned

[FW][IMP] l10n_my_edi_extended: TIN and refund

[FW][FIX] account: add loop detection to bounce

[FW][FIX] l10n_eu_oss_reports: Ensure unique line IDs

[FW][IMP] pos_restaurant_appointment: Add minimal html editor in pos mode

[FW][ADD] l10n_be_hr_payroll_prisma: new module

[FW][FIX] account_sepa_direct_debit: Fix SDD notification mail language

[FW][FIX] project_enterprise: fix test that depends on timesheet modules

[FW][FIX] l10n_es_reports: VAT Record Books export: properly handle entries with multiple similar tax lines

[FW][IMP] l10n_nl_reports: allow defining custom start dates for the tax closings in the Netherlands

[FW][FIX] l10n_mx_edi_pos: fix refund crash when the order is invoiced

[FW][FIX] l10n_de_pos_cert: fix payment type fiskaly

[FW][FIX] stock_barcode: scan lot in kanban

[FW][FIX] sign: add template_id as query parameter

[FW][FIX] account_followup: Fix sms reminders in customer's language

[FW][FIX] stock_barcode: don't display Sign button for batch picking

[FW][FIX] l10n_co_dian: handle odoo and DIAN being out of sync

[FW][FIX] account_bank_statement_import_camt: handle more multi-currency …

[FW][FIX] pos_restaurant_appointment: restaurant_appointment_tour