Daily updates from Odoo
Monday, March 2, 2026
8 changes · 17.0
Resolved issues and error corrections
This update resolves an issue where foreign vendor VAT invoices were not correctly identifying the country of origin. The fix adds the necessary country code to vendor bills, ensuring accurate reporting for Polish VAT compliance. This improves the accuracy of JPK reports.
Original PR description
PR #81359 fixed the country code for foreign VAT companies by adding the country code to the start. However, this was only fixed for invoices going out, not vendor bills coming in. [opw-5917264](https://www.odoo.com/odoo/project.task/5917264)
This update fixes an issue where negative values were appearing in the tax report XML for carried over tax lines. The change ensures that these lines are generated correctly without negative amounts, improving report accuracy and data consistency. This resolves a previous bug reported as opw-5955323 and opw-5428395.
Original PR description
When generating the xml for tax report, negative values should not be present in the xml for carried over lines (81, 82, 83, 86, 87, and 88) Steps: - Create a RBILL for today - 1 month, add an invoice line with tax using one of the following tags: -81, -82, -83, -86, -87 or -88 in its base refund repartition line - Open the tax report on the month of the RBILL - Generate the xml, either by the dedicated button, or by creating and posting the closing entry -> there is line(s) for negative amounts opw-5955323 opw-5428395
This update corrects a technical issue where PDF attachments were sometimes displayed with a zero size. The fix ensures the attachment size is correctly interpreted, preventing display problems. This improvement ensures PDFs are correctly rendered within Odoo.
Original PR description
Currently, the size parameter of the embedded file is defined as a NameObject. This is leading some readers to not interpreting it as an Integer value and results in a zero size for the attachment. A fix was implemented in versions 18 and above (https://github.com/odoo/odoo/pull/248769), this is a backport of it. opw-5928269 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where payslip line creation was failing in the stable version of Odoo Enterprise. The fix reintroduces a necessary step to ensure accurate data processing, preventing errors and improving the overall stability of payroll processing. This ensures correct payroll calculations and reporting.
Original PR description
Related is not applied correctly in stable after https://github.com/odoo/enterprise/pull/108729, leading to a missing field error, we reintroduce it for stability reasons
This pull request partially reverses a recent change that caused tax predictions to fail. Previously, taxes were calculated once, but the system no longer correctly predicted the associated accounts. This fix addresses a bug introduced by a previous update, restoring the expected account prediction functionality.
Original PR description
…x at import" Bug introduced by: https://github.com/odoo/odoo/commit/9cc26a154381e51e3f4188aa7c251d959538676e Since this, the taxes are predicted only once but the prediction of account is no longer working. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a minor efficiency issue within the Odoo accounting module. Previously, a check was performed on multiple records when it should have been done on a single record. This change ensures the system operates more efficiently and avoids potential performance impacts.
Original PR description
In some cases, the check was done on multiple records, though the method should be called on one and only one record.
This update resolves a problem with generating CSV reports for Peru-specific accounting modules. The issue stemmed from incompatible CSV formatting settings, triggered during automated testing. The fix simplifies the configuration and ensures consistent report output.
Original PR description
Revealed when l10n modules got enabled on the "distro builds" nightly: on Trixie, `delimiter="|", lineterminator='|\n'` raises ValueError: bad delimiter or lineterminator value This is due to…
Revealed when l10n modules got enabled on the "distro builds" nightly: on Trixie, `delimiter="|", lineterminator='|\n'` raises
ValueError: bad delimiter or lineterminator value
This is due to python/cpython#113797 which added new validations to dialect definitions. For this issue, that the delimiter can not be in the line terminator. This can be fixed via a different trick, which is documented:
> The optional `restval` parameter specifies the value to be written
> if the dictionary is missing a key in `fieldnames`.
so if we add a trailing fieldname which *can not* be found in the row dicts, then `DictWriter` will always write out an empty trailing cell (the default `restval` is an empty string), which should result in the same output.
Also remove the `csv.register_dialect` calls, that's so subsequent CSV calls can easily refer to a common configuration but here two different dialects are being registered under the same name, and each one is only used for the following `DictWriter` call, so at best this is a complete waste of time and at worst this is a race condition in threaded configurations. Just pass the formatting parameters directly to the `DictWriter`.
https://runbot.odoo.com/odoo/error/240950Features or functions removed from Odoo
This update removes a now-unnecessary field ('Visible Internally Only') from the customer rating form in the Helpdesk module. Since customer ratings are no longer displayed on the website, this field was causing confusion and clutter. This change improves the user experience and simplifies the Helpdesk interface.
Original PR description
**Steps to reproduce:** - Open a Helpdesk ticket with a customer rating. - View the rating form. - Observe the field ‘Visible Internally Only’ still showing. **Issue:** - The field is displayed even though ratings are no longer shown on the website. **Reason:** - The field is now irrelevant but still present in the view. **Fix:** - Invisible the ‘Visible Internally Only’ field from the customer rating form in the affected version. **Task id - 5359052**