Thursday, December 4, 2025
2 changes · 18.0
Enhancements to existing features
This update ensures greater clarity and accuracy in Odoo's queries by consistently using fully qualified column names (e.g., `account_move.balance`). This prevents ambiguity when joining tables and avoids potential issues with custom modules, ultimately strengthening data reliability.
Original PR description
Use fully qualified column names when constructing a query, more specifically, include the table that the column is originating from. The rule of thumb is that we always include the table name alongside the column name. In this particular case, the query will do a `JOIN` on `account_move` and there may be ambiguousness as to whether to take the `balance` column from `account_move` or `account_move_line`. The former column used to exist in the past and was likely kept for data retention purposes. Hence, there are still databases in 17.0 where `account_move.balance` exists. Another reason to include the table name is to prevent confusion with columns coming from custom modules. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#237181
This update clarifies the labeling of a field used when making salary adjustments within the HR payroll module. The change ensures users understand exactly where this input is accessible, leading to a more intuitive and efficient adjustment process. This improves usability and reduces potential errors.
Original PR description
This change ensures the label accurately reflects where the field is accessible and providing better clarity for users when working with salary adjustments. Task: 5375187