Odoo Changelog — 2025-12-21

Sunday, December 21, 2025

2 changes · saas-18.4

Bug Fixes(2)

Resolved issues and error corrections

[FIX] account_peppol: no focusing on eas field

Coresaas-18.4account_peppol

This update resolves an issue where the ‘eas’ field was incorrectly focused during Peppol registration. By removing the ability to focus this field, the registration process is now streamlined and ensures users correctly select the pre-selected option, improving the user experience and data accuracy.

Original PR description

During registration on Peppol, the eas field is focused first, which makes no sense as it's supposed to be correctly preselected, and users aren't supposed to touch it

So this commit makes it non-focusable

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

Forward-Port-Of: odoo/odoo#240747
Forward-Port-Of: odoo/odoo#240679

#peppol#registration#account

[FIX] account_update_tax_tags: add company field

PR #238369

Coresaas-18.4account_update_tax_tagsMEDIUM

A recent update to the ‘Update Tax Tags’ wizard in Odoo v18 was causing it to crash when a company had a tax lock date configured. This fix reintroduces a previously used element to ensure the wizard correctly loads company information and calculates the warning date, resolving the crash and restoring functionality.

Original PR description

Opening the `Update Tax Tags` wizard in v18 crashes when the company has a tax lock date configured, raising:

```
TypeError: '<' not supported between instances of 'bool' and 'datetime.date'
```

The error happens because `_compute_display_lock_date_warning` is evaluated while date_from is still False, so the comparison `wizard.date_from < tax_lock_date` ends up comparing a boolean with a date. In v17 the wizard form view included an invisible company_id field, which ensured the company was properly loaded in the cache and allowed `_compute_date_from` to run with the correct company_id and tax_lock_date before the warning compute was triggered.

This change reintroduces the invisible company_id field in the wizard form view to restore the v17 behavior. The wizard now loads the company correctly, computes `date_from` based on the tax lock date, and then computes `display_lock_date_warning` without triggering the TypeError.






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

Forward-Port-Of: odoo/odoo#238005

#tax#update#wizard

During registration on Peppol, the eas field is focused first, which makes no sense as it's supposed to be correctly preselected, and users aren't supposed to touch it So this commit makes it non-focusable 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 Forward-Port-Of: odoo/odoo#240747 Forward-Port-Of: odoo/odoo#240679

Opening the `Update Tax Tags` wizard in v18 crashes when the company has a tax lock date configured, raising: ``` TypeError: '<' not supported between instances of 'bool' and 'datetime.date' ``` The error happens because `_compute_display_lock_date_warning` is evaluated while date_from is still False, so the comparison `wizard.date_from < tax_lock_date` ends up comparing a boolean with a date. In v17 the wizard form view included an invisible company_id field, which ensured the company was properly loaded in the cache and allowed `_compute_date_from` to run with the correct company_id and tax_lock_date before the warning compute was triggered. This change reintroduces the invisible company_id field in the wizard form view to restore the v17 behavior. The wizard now loads the company correctly, computes `date_from` based on the tax lock date, and then computes `display_lock_date_warning` without triggering the TypeError. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238005