Odoo Changelog — 2025-04-24

Thursday, April 24, 2025

45 changes · saas-18.2

Bug Fixes(3)

Resolved issues and error corrections

[FIX] pos_urban_piper: replace row match logic

Enterprisesaas-18.2pos_urban_piper

This update adjusts automated checks for UrbanPiper point-of-sale orders so they look for order text more reliably. It helps reduce false test failures without changing the customer-facing ordering experience.

Original PR description

In this commit:
===
- Replaced all occurrences of  `TicketScreen.nthRowContains()` with `UrbanPiper.orderHasText()` in test tours.

task-4712861
runbot-115061

#pos#urban-piper#testing

[FIX] documents: hide share button for portal users

PR #83306

Enterprisesaas-18.2documents

Portal users will no longer see a Share button that they cannot use in Documents. This removes confusion and keeps the portal view aligned with the actions actually available to those users.

Original PR description

**Before this PR:**
The Share panel is not accessible to portal users, but the Share button is still visible to them.

**After this PR:**
The Share button will no longer be visible in the portal view.

Task-4717553

#portal#sharing#user interface

[FIX] html_editor: prevent column selection on table border double-click

PR #206251

Coresaas-18.2html_editor

Double-clicking a table border in the HTML editor no longer selects an entire column or triggers an error when the cursor is outside the table. This makes table editing more predictable and prevents a disruptive crash scenario for users editing content.

Original PR description

**Current behavior before PR:**

- Double-clicking on a table border would select the table column if the selection was inside a table cell.
- If the selection was outside the table, a traceback will occur.

**Desired behavior after PR is merged:**

- Now, a table cell is now only selected when the double-click is performed inside the cell, not on its border.

task:4730234

#html editor#tables#selection

Other(42)

Miscellaneous changes

[FW][FIX] test_performance: non-deterministic results

PR #207176

Coresaas-18.2test_performance

Some of the tests are not deterministic on the runbot. Avoid raising errors in these cases. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#206812 Forward-Port-Of: odoo/odoo#206669

Original PR description

Some of the tests are not deterministic on the runbot. Avoid raising errors in these cases.



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

Forward-Port-Of: odoo/odoo#206812
Forward-Port-Of: odoo/odoo#206669

[FW][FIX] l10n_hu_edi: invoice spacing

PR #207102

**Before this PR:** The Share panel is not accessible to portal users, but the Share button is still visible to them. **After this PR:** The Share button will no longer be visible in the portal view. Task-4717553

**Current behavior before PR:** - Double-clicking on a table border would select the table column if the selection was inside a table cell. - If the selection was outside the table, a traceback will occur. **Desired behavior after PR is merged:** - Now, a table cell is now only selected when the double-click is performed inside the cell, not on its border. task:4730234

Before this commit, when the user enables the task dependencies feature globally, all basic projects (that is, non fsm ones) will get the feature. By doing that, the open tasks state will be recomputed to set `Waiting` state on tasks with blocking tasks linked to them. The problem is the compute method of the task state will also reset the state instead of keeping the one set on those open tasks when there is no blocking task linked. This commit makes sure the compute method of task state field is no longer called when the task dependencies feature changes. Instead, a inverse method is added on allow_task_dependencies field on `project.project` model to correctly update the state of the tasks linked to the project in which the task dependencies feature changed. Steps to reproduce the issue: ---------------------------- 0. install project 1. Create a project 2. Create some tasks inside that project and changes the state to some tasks 3. Enable the task dependencies feature in `Project > Configuration > Settings` menu. 4. Go back to the tasks kanban view of that project. Current Behavior: ---------------- The state of those tasks is reset to `In progress` (if those tasks did not have a state equals to `Done` or `Canceled`). Expected Behavior: ----------------- The state of those tasks should not be altered since no dependencies are added in those tasks yet. task-4487922 Forward-Port-Of: odoo/odoo#206560 Forward-Port-Of: odoo/odoo#198952

Steps to reproduce the issue: - Create a storable product “P1” - Create a Bill of Materials: - Finished product: 1 unit of P1 - Components: - 1 unit of C1 - Create a manufacturing order to produce 10 units of P1 - Confirm the MO - Split the MO into two: - This creates two new MOs, each for 5 units: - “WH-MO-001” - ”WH-MO-002” - For the first MO (WH-MO-001): - Set Quantity Produced to 1. - Validate it and choose to create a backorder. Problem: - The backorder is incorrectly named “WH-MO-001-003” instead of the expected WH-MO-003. - Additionally, the original MO is renamed “WH-MO-001-001”, which is unexpected. - However, if you perform the same steps on the second MO (WH-MO-002), the backorder is correctly named “WH-MO-003”, and the original name remains unchanged. Root cause: - When the original MO is first split, each resulting MO receives a backorder sequence: - First split MO (WH-MO-001): backorder_sequence = 1 - Second split MO (WH-MO-002): backorder_sequence = 2 - When creating a backorder from an MO with backorder_sequence = 1, the following logic is triggered: - https://github.com/odoo/odoo/blob/18.0/addons/mrp/models/mrp_production.py#L1844 - Since the condition if backorder_sequence > 1 is false for WH-MO-001: - https://github.com/odoo/odoo/blob/18.0/addons/mrp/models/mrp_production.py#L1782 - So the name + seq_back is added: https://github.com/odoo/odoo/blob/18.0/addons/mrp/models/mrp_production.py#L1784 opw-4686959 Forward-Port-Of: odoo/odoo#205760

**Steps to reproduce:** - Install Accounting - Activate a foreign currency (e.g. EUR) - Make sure there are several rates with today rate different than others - Go to "Accounting / Configuration / Accounting / Chart of Accounts" - Add a default tax to "Expenses" account - Create an invoice: * Customer: [any] * Currency: [EUR] (i.e. the foreign currency) * Invoice Date: [a date in the past where the currency rate is different than today] * Invoice Lines: [any] - Confirm the invoice - Go to "Accounting / Reporting / Management / Unrealized Currency Gains/Losses" - Set date filter to "Today" - If there is no adjustement to do, check if the following message is displayed: "You are using custom exchange rates. => Reset to Odoo’s Rate" If it's the case, reset to Odoo's rate (i.e. Today's rate) - Click on "Adjustement Entry" button: * Journal: Miscellaneous Operations * Expense Account: Expenses * Income Account: [any] - Create Entry **Issue:** The values (debit/credit) of the created entry are 0, which is not the case when there is no default tax on the expense account. **Cause:** "_sync_dynamic_lines" is executed on the created entry. If a default tax is set on the expense account, "_sync_tax_lines" is also executed. As only debit and credit values are set on the invoice lines of the entry (neither balance nor amount_currency), the sync method messes up with the value of debit and credit, resetting them to 0 (via multiple recompute). **Solution:** Skip invoice sync. The values computed in "Multicurrency Revaluation Wizard" should be the ones that are used. opw-4664255 Forward-Port-Of: odoo/enterprise#83570

**Steps to reproduce:** - Install Accounting - In Bank journal settings, make sure that there's no Outstanding Payments account - Create a bill for a customer - Confirm it - Create a second bill for the same customer - Confirm it - Go to the bills list - Select the 2 created bills - Create a payment via "Pay" button: * Journal: Bank * Payment Method: Manual Payment * Group Payments: [checked] - Do not validate the payment - Go to "Accounting / Vendors / Payments" - Select the created payment and create a batch - Validate the batch payment => The payment status of both bills is "In Payment" - From Accounting dashboard, go to transactions of Bank journal (reconciliation widget) - Create a new transaction for the previous customer with the amount of the batch payment - In the reconciliation widget, go to "Batch Payments" tab - Select the created batch payment - Validate to reconcile - Check the bills list **Issue:** Only one of the bills has its payment status set to "Paid", the other one staying in "In Payment" status. **Cause:** In the method that checks which account move lines are included in the batch payment, we loop on each linked move line and take the "min" between the remaining amount of the batch payment and the amount of the move line until the remaining amount reaches 0. However, for vendor bills, these amounts are negative and taking the "min" amount returns the remaining amount directly, resulting in only having 1 move line set to reconcile. opw-4595006 Forward-Port-Of: odoo/enterprise#83634

According to [last update from PGCE](https://www.boe.es/buscar/act.php?id=BOE-A-2007-19884&tn=1&p=20241221) and the accounting standards inside it: >3.º Principios contables La contabilidad de la empresa y, en especial, el registro y la valoración de los elementos de las cuentas anuales, se desarrollarán aplicando obligatoriamente los principios contables que se indican a continuación: > >1. Empresa en funcionamiento. Se considerará, salvo prueba en contrario, que la gestión de la empresa continuará en un futuro previsible, por lo que la aplicación de los principios y criterios contables no tiene el propósito de determinar el valor del patrimonio neto a efectos de su transmisión global o parcial, ni el importe resultante en caso de liquidación. > >En aquellos casos en que no resulte de aplicación este principio, en los términos que se determinen en las normas de desarrollo de este Plan General de Contabilidad, la empresa aplicará las normas de valoración que resulten más adecuadas para reflejar la imagen fiel de las operaciones tendentes a realizar el activo, cancelar las deudas y, en su caso, repartir el patrimonio neto resultante, debiendo suministrar en la memoria de las cuentas anuales toda la información significativa sobre los criterios aplicados. > >2. Devengo. Los efectos de las transacciones o hechos económicos se registrarán cuando ocurran, imputándose al ejercicio al que las cuentas anuales se refieran, los gastos y los ingresos que afecten al mismo, con independencia de la fecha de su pago o de su cobro. > >3. Uniformidad. Adoptado un criterio dentro de las alternativas que, en su caso, se permitan, deberá mantenerse en el tiempo y aplicarse de manera uniforme para transacciones, otros eventos y condiciones que sean similares, en tanto no se alteren los supuestos que motivaron su elección. De alterarse estos supuestos podrá modificarse el criterio adoptado en su día; en tal caso, estas circunstancias se harán constar en la memoria, indicando la incidencia cuantitativa y cualitativa de la variación sobre las cuentas anuales. > > 4. Prudencia. Se deberá ser prudente en las estimaciones y valoraciones a realizar en condiciones de incertidumbre. La prudencia no justifica que la valoración de los elementos patrimoniales no responda a la imagen fiel que deben reflejar las cuentas anuales. > > Asimismo, sin perjuicio de lo dispuesto en el artículo 38 bis del Código de Comercio, únicamente se contabilizarán los beneficios obtenidos hasta la fecha de cierre del ejercicio. Por el contrario, se deberán tener en cuenta todos los riesgos, con origen en el ejercicio o en otro anterior, tan pronto sean conocidos, incluso si sólo se conocieran entre la fecha de cierre de las cuentas anuales y la fecha en que éstas se formulen. En tales casos se dará cumplida información en la memoria, sin perjuicio de su reflejo, cuando se haya generado un pasivo y un gasto, en otros documentos integrantes de las cuentas anuales. Excepcionalmente, si los riesgos se conocieran entre la formulación y antes de la aprobación de las cuentas anuales y afectaran de forma muy significativa a la imagen fiel, las cuentas anuales deberán ser reformuladas. > > Deberán tenerse en cuenta las amortizaciones y correcciones de valor por deterioro de los activos, tanto si el ejercicio se salda con beneficio como con pérdida. > > 5. No compensación. Salvo que una norma disponga de forma expresa lo contrario, no podrán compensarse las partidas del activo y del pasivo o las de gastos e ingresos, y se valorarán separadamente los elementos integrantes de las cuentas anuales. > > 6. Importancia relativa. Se admitirá la no aplicación estricta de algunos de los principios y criterios contables cuando la importancia relativa en términos cuantitativos o cualitativos de la variación que tal hecho produzca sea escasamente significativa y, en consecuencia, no altere la expresión de la imagen fiel. Las partidas o importes cuya importancia relativa sea escasamente significativa podrán aparecer agrupados con otros de similar naturaleza o función. > > En los casos de conflicto entre principios contables, deberá prevalecer el que mejor conduzca a que las cuentas anuales expresen la imagen fiel del patrimonio, de la situación financiera y de los resultados de la empresa. For item 5, assets and liabilities, income and expenses shall not be offset, unless required or permitted by a standard. Therefore, group 55 accounts should be presented: - On the assets side if they have a debit balance. - On the liabilities side if they have a credit balance. - Without offsetting each other. @moduon MT-9820 @chklop @jco-odoo @rafaelbn Forward-Port-Of: odoo/enterprise#82976

Bug Fixes(3)

[FIX] pos_urban_piper: replace row match logic

[FIX] documents: hide share button for portal users

[FIX] html_editor: prevent column selection on table border double-click

Other(42)

[FW][FIX] test_performance: non-deterministic results

[FW][FIX] l10n_hu_edi: invoice spacing

Bug Fixes(3)

[FIX] pos_urban_piper: replace row match logic

[FIX] documents: hide share button for portal users

[FIX] html_editor: prevent column selection on table border double-click

Other(42)

[FW][FIX] test_performance: non-deterministic results

[FW][FIX] l10n_hu_edi: invoice spacing

[FW][FIX] hw_drivers: incorrect rpc result browsing

[FW][FIX] web: Chrome 135 + HOOT ; click or not click, that is the question

[FW][FIX] {stock,mrp}_account: unbuild after return

[FW][FIX] web_editor: give correct error for too large image upload

[FW][FIX] account: update journal and sequence when changing payment journal

[FW][FIX] account_check_printing: access error with branch

[FW][FIX] l10n_cl: vat format on invoice report

[FW][IMP] hw_drivers: new way to detect IoT

[FW][FIX] stock{,_dropshipping}: report customer lots from dropships

[FW][FIX] payment_asiapay: Add missing payment methods

[FW][FIX] web_editor, *: resolve visibility issue at initial stage

[FW][FIX] hr_expense: don't raise when not found

[FW][FIX] website_sale: make Tags filter collapsible and adjust margin

[FW][FIX] digest: fix view inheritence

[FW][FIX] hr_timesheet_attendance: fix the timezone related issue

[FW][IMP] account: add placeholder for eInvoice format

[FW][FIX] project: enable task dependencies feature should not reset task state

[FW][FIX] mrp: generate backorder names correctly

[FW][FIX] web_editor: make the date clearly visible

[FW][FIX] point_of_sale: correctly compute extra price for attributes

[FW][FIX] web_tour: tour stuck on dropdown loading

[FW][FIX] l10n_co_edi_website_sale: NIT search update

[FW][REM] *: checkDelay is no longer used

[FW][FIX] account_3way_match: correct unpaid amount on dashboard

[FW][FIX] l10n_be_hr_payroll: onss number field is Char

[FW][FIX] account_reports: select current company when sending multiple customer statements

[FW][REV] l10n_cl: vat format on invoice report

[FW][FIX] spreadsheet_edition: update doesn't drop sorting

[FW][FIX] account_reports: fix adjustment entry in unrealized currency gains report

[FW][FIX] worksheet : duplicate worksheet template breaking reports

[FW][FIX] test_l10n_be_hr_payroll_account: add wait steps for tour

[FW][FIX] web_studio: improve visibility of technical name in dark mode

[FW][IMP] l10n_ch_hr_payroll_elm_transmission: Add various wage types

[FW][FIX] l10n_us_hr_payroll_account: Correctly import missing views

[FW][FIX] l10n_be_hr_payroll: multi record sdworx code check

[FW][FIX] approvals_purchase: correctly update product seller

[FW][FIX] account_accountant_batch_payment: all bills in batch payment without JE reconciliation

[FW][FIX] l10n_ca_payment_cpa005: test ACLs

[FW][FIX] l10n_es_reports: The accounts of group 55 must not be offset against each other

[FW][REM] *: checkDelay is no longer used