Monday, May 4, 2026
5 changes · 18.0
Resolved issues and error corrections
This update resolves a problem with the Intrastat CSV export in the Dutch localization module. The technical changes corrected an issue where commodity flow data was incorrectly formatted and a database refresh was added to ensure accurate export data. This ensures reliable reporting for Intrastat compliance.
Original PR description
Since the technical refactoring of intrastat in 18.0, the csv export in `l10n_nl_intrastat` seems broken. Here is the fixes done in this commit: 1. `Commodity flow` is supposed to be a single diggit (6 or 7) but an empty blank space was hidden. 2. Switching the condition on `country_origin_code` as it was the opposite 3. Add a `flush_all` before calling the report during the export, to be sure the database is up to date. opw-5799126
This update fixes an issue where the CustomGroupByItem dropdown in the search bar wasn't correctly styled on hover. The fix ensures the dropdown items appear as expected and also restores keyboard navigation functionality for this feature. This improves the overall user experience of the search functionality.
Original PR description
The CustomGroupByItem select was missing the `o-navigable` class, so the navigation system never registered it. On hover, it would not receive the `focus` class, which ensures proper styling of dropdown items. The fix also restores the ability to reach the CustomGroupByItem select with keynav. task-6108677
This update resolves a duplication issue in the French Profit & Loss report by removing a redundant account (6492) that was previously included alongside account 649. This ensures accurate financial reporting for French businesses using the Odoo Enterprise system.
Original PR description
This commit is an addon to this commit[[1]] where we tried to avoid duplicate accounts in the Profit And Loss report. The problem is that we don't exclude the separated account 6492 from the original one (649). This commit adds the removal of this account in the report formula. task-6053784 Here is the coverage: [Profit and loss account (FR) - Accounts Coverage Report (2).xlsx](https://github.com/user-attachments/files/27011824/Profit.and.loss.account.FR.-.Accounts.Coverage.Report.2.xlsx) The correct separation: <img width="837" height="485" alt="image" src="https://github.com/user-attachments/assets/ebe98976-f689-4389-866a-c9a0c8b50534" /> [1]: https://github.com/odoo/enterprise/commit/4587c49c4b220305652150d2f21a95fb7cfa188d Forward-Port-Of: odoo/enterprise#114858
This change reverts a recent update to Odoo's unit of measure (UoM) rounding method. The initial change was deemed too risky and caused a test failure, potentially leading to unexpected issues. We're now investigating a more targeted solution to ensure accurate UoM calculations.
Original PR description
This reverts commit 5dbb814. The commit seems too risky for stable, it broke a test in 18.2 which was recently modified only in 18.0 (see 8ba1214, not sure why it wasn't fw-ported). There is a chance it breaks other stuff silently. We'll look for a more local fix that doesn't affect other use cases.
This update resolves an issue where new company contacts created through invoices still incorrectly included DnB industry data (UNSPSC) as partner tags. The fix ensures that company creation from Partner many2one views aligns with the standard contact form, preventing unnecessary IAP credit usage. This improves data consistency and efficiency.
Original PR description
Partner Autocomplete was updated so DnB industry data (UNSPSC) is no longer stored on Partner Tags. That behavior was applied to the name/VAT char widget, but creating a company from a Partner…
Partner Autocomplete was updated so DnB industry data (UNSPSC) is no longer stored on Partner Tags. That behavior was applied to the name/VAT char widget, but creating a company from a Partner many2one (e.g. customer/vendor on an invoice) still used the old path: calling an IAP suggestion `iap_partner_autocomplete_add_tags` Steps to reproduce: ------------------- * Open a customer invoice (draft). * On Customer, search a company name and pick a Partner Autocomplete line to create a new company. * Save the quick-create dialog. > Observation: The new contact still had Partner Tags populated from DnB industry data (UNSPSC), unlike contacts created or enriched from the contact form autocomplete. (see video on ticket to avoid using more IAP credits) Why the fix: ------------ Align `res_partner_many2one` with `field_partner_autocomplete`: do not call `iap_partner_autocomplete_add_tags`. From task-5373200, industries from DnB must no longer be added as Partner Tags. opw-5972360