Odoo Changelog — 2025-11-06

Thursday, November 6, 2025

3 changes · master

Improvements(3)

Enhancements to existing features

[WIP]

Enterprisemasterweb_studio

This change updates part of Web Studio’s field property editor, specifically the area used to configure type-specific and computed field settings. Because the pull request is still marked as work in progress and has limited detail, the business impact appears minor and focused on improving the Studio editing experience.

#web studio#field configuration#work in progress

[IMP] account_reports: add possibility to join currency table on query

PR #94886

Enterprisemasteraccount_intrastataccount_reportsaccount_reports_cash_basisl10n_bg_reports_ledgerl10n_es_reportsl10n_mx_xml_polizasl10n_ph_reportsl10n_vn_reportsmrp_account_enterprise

Financial reporting queries were updated so currency conversion data can be added more consistently across reports. This is mainly an internal improvement that makes report generation logic cleaner and easier to maintain, with no expected change to day-to-day user workflows.

Original PR description

This is a syntaxic change. The first change is to allow the currency table to be joined on a `Query` object. This was not possible because `_currency_table_aml_join` returned raw sql. This is a…

This is a syntaxic change.

The first change is to allow the currency table to be joined on a
`Query` object.  This was not possible because
`_currency_table_aml_join` returned raw sql.
This is a syntax improvement, as it then allows to fully exploit
the `Query` class methods, notably `select`, which generates the SQL
directly from the object.  Without having to write
`SQL("SELECT %s FROM %s WHERE %s GROUP BY %s", ...)`.
In order to do this change, `_get_monocurrency_currency_table_sql` had
to be modified, as the sql returned by this method could not be
understood by the `Query` object.  Not possible to join a table that is
created on the fly.  That is because it expects an alias to be an
identifier, and not something of the form
`account_currency_table(company_id, ...)`.

Because of this change, it is possible to do a second syntax
improvement, which is to directly join the currency table on the `Query`
object created in `_get_report_query`.  This is done by setting the new
kwarg `join_currency_table` to `True`.

Community PR: https://github.com/odoo/odoo/pull/227398

#financial reports#currency#maintainability

[IMP] {l10n_mx_,}hr_payroll_account{_edi,}: rename "Create Draft Entry" into "Validate"

PR #98911

Enterprisemasterhr_payroll_accountl10n_mx_hr_payroll_account_edi

The payroll interface now uses the clearer label "Validate" instead of "Create Draft Entry" on related payslip and pay run actions. This makes the next step in payroll processing easier for users to understand, including in the Mexico payroll accounting flow.

Original PR description

Task-ID: 5226530

#payroll#accounting#user interface

This is a syntaxic change. The first change is to allow the currency table to be joined on a `Query` object. This was not possible because `_currency_table_aml_join` returned raw sql. This is a syntax improvement, as it then allows to fully exploit the `Query` class methods, notably `select`, which generates the SQL directly from the object. Without having to write `SQL("SELECT %s FROM %s WHERE %s GROUP BY %s", ...)`. In order to do this change, `_get_monocurrency_currency_table_sql` had to be modified, as the sql returned by this method could not be understood by the `Query` object. Not possible to join a table that is created on the fly. That is because it expects an alias to be an identifier, and not something of the form `account_currency_table(company_id, ...)`. Because of this change, it is possible to do a second syntax improvement, which is to directly join the currency table on the `Query` object created in `_get_report_query`. This is done by setting the new kwarg `join_currency_table` to `True`. Community PR: https://github.com/odoo/odoo/pull/227398