Odoo Changelog — 2026-08-20

Thursday, August 20, 2026

2 changes · saas-19.3

Improvements(2)

Enhancements to existing features

[PERF] project: speed up portal task search

Coresaas-19.3projectMEDIUM

Portal task searches now avoid a slow lookup pattern that forced the system to scan all tasks. Users should see much quicker results when searching task lists, especially in large databases.

Original PR description

The portal task list searched titles with
['|', ('name', 'ilike', search), ('id', 'ilike', search)]. Applying ilike to the integer id casts it to text, which no index can serve, and OR-ing that branch with the title prevents the trigram index on name from being used at all, so every search fell back to a full scan of project_task. The id branch is now added only when the term is numeric, as an equality on the primary key, keeping the title lookup on its trigram index.

Benchmark on 200k tasks, PostgreSQL EXPLAIN ANALYZE, selective term matching 5 rows, median of 3 runs:

  before   Parallel Seq Scan on project_task    ~150 ms
  after    Bitmap Index Scan (name gin_trgm_ops)  ~0.5 ms

opw-5478903

Forward-Port-Of: odoo/odoo#278548

#performance#portal#tasks#search

[IMP] account: improve context in FEC import validation errors

PR #283279

Coresaas-19.3accountMEDIUM

Accounting validation errors now include more useful details, such as the affected account code or journal entry reference. This makes FEC imports and related accounting troubleshooting faster because users can identify the problematic record more easily.

Original PR description

Some generic validation errors raised by core account models lack enough context to identify which record caused the issue, making FEC imports harder to troubleshoot. This commit improves the two…

Some generic validation errors raised by core account models lack enough context to identify which record caused the issue, making FEC imports harder to troubleshoot.

This commit improves the two error cases identified for this use case:
- `account.account._check_account_code` now includes the invalid account code in the error message.
- `account.move.write` now includes the move name/reference and displays human-readable field labels instead of technical field names when attempting to modify read-only fields on posted entries.

Although motivated by FEC import, these are generic core validations, so the improvements are implemented at the source to benefit all callers rather than only the FEC import flow.

Enrichment is scoped to the two cases above, other constraints/errors across these models are intentionally left unchanged for now, since editing core error messages more broadly should be done deliberately and on a case-by-case basis, not as a blanket rewrite

task-5346068

Forward-Port-Of: odoo/odoo#282840
Forward-Port-Of: odoo/odoo#281746

#accounting#imports#validation#error messages

The portal task list searched titles with ['|', ('name', 'ilike', search), ('id', 'ilike', search)]. Applying ilike to the integer id casts it to text, which no index can serve, and OR-ing that branch with the title prevents the trigram index on name from being used at all, so every search fell back to a full scan of project_task. The id branch is now added only when the term is numeric, as an equality on the primary key, keeping the title lookup on its trigram index. Benchmark on 200k tasks, PostgreSQL EXPLAIN ANALYZE, selective term matching 5 rows, median of 3 runs: before Parallel Seq Scan on project_task ~150 ms after Bitmap Index Scan (name gin_trgm_ops) ~0.5 ms opw-5478903 Forward-Port-Of: odoo/odoo#278548

Some generic validation errors raised by core account models lack enough context to identify which record caused the issue, making FEC imports harder to troubleshoot. This commit improves the two error cases identified for this use case: - `account.account._check_account_code` now includes the invalid account code in the error message. - `account.move.write` now includes the move name/reference and displays human-readable field labels instead of technical field names when attempting to modify read-only fields on posted entries. Although motivated by FEC import, these are generic core validations, so the improvements are implemented at the source to benefit all callers rather than only the FEC import flow. Enrichment is scoped to the two cases above, other constraints/errors across these models are intentionally left unchanged for now, since editing core error messages more broadly should be done deliberately and on a case-by-case basis, not as a blanket rewrite task-5346068 Forward-Port-Of: odoo/odoo#282840 Forward-Port-Of: odoo/odoo#281746