Wednesday, September 17, 2025
3 changes · 17.0
Resolved issues and error corrections
This fixes incorrect Spanish translations for Peruvian electronic invoicing and stock-related tariff and withholding fields. Users working in Spanish will see clearer, more accurate labels, reducing confusion in local compliance workflows.
Original PR description
## Issue: The latest `tariff_fraction` entries were not properly translated into Spanish There were also inconsistencies in the translation of some `withhold codes` ## Cause: The `.po` and `.pot` files were not correctly populated In addition, the translation of "Others" in `l10n_pe_withhold_code` conflicted with `l10n_pe_edi_reason_for_transfer__13`, because the `msgid` is the same but not the `msgstr` should be different opw-4741731
The Mail app no longer offers an unsupported company grouping option for alias domains. This prevents users from hitting an error when using the Group By menu, making the view more reliable.
Original PR description
Currently, an exception is generated when the user tries to group by copmany in Alias Domain. Error: `psycopg2.errors.UndefinedColumn: column mail_alias_domain.company_ids does not exist` This is because the search view of the `mail.alias.domain` model is used group by company_ids field, which is One2many. This commit will fix above issue by removing the company_ids from the group since we can't group by records with multiple record set fields. sentry-5774171054
Saving the Statement report in Studio no longer fails when there are no existing statement records to provide a currency. The system now uses the current company's currency as a fallback, helping users work with reports reliably in new databases.
Original PR description
Currently, an exception is generated when the user tries to save the "statement" report in Studio. Steps to produce an error: - Create DB without a demo and install 'web_studio' and 'account_reports' - Open Accounting and click on studio icon - Click Reports > Remove values from searchbar > Open "STATEMENT" report - edit anything > Click on save >>> Error generated This is because line [1] tries to get the display currency from the record (which is the "currency_id" field), but since without demo we do not have any record in account statement, it tries to get value from 'NewId' and no value is available in field 'currency_id'. This commit will fix the above issue by setting the current company currency as display currency if not currency available in record. [1] - https://github.com/odoo/odoo/blob/d1f20d6b71203e6bb4b428ae1bcbb0b76e739f51/odoo/addons/base/models/ir_qweb_fields.py#L512 sentry-5639835599