Wednesday, July 1, 2026
5 changes · 18.0
Resolved issues and error corrections
This update adjusts the order of elements in the Mexican SAT XML trial balance report so it matches the structure recommended by the tax authority. The report content remains the same, but the generated file now follows the expected layout more closely, reducing the risk of compliance or validation issues.
Original PR description
**Steps to reproduce:** - Install the `l10n_mx_reports` module and switch to a Mexican company. - Navigate to Accounting > Reporting > Trial Balance. - From the dropdown menu, click `SAT (XML)`. -…
**Steps to reproduce:** - Install the `l10n_mx_reports` module and switch to a Mexican company. - Navigate to Accounting > Reporting > Trial Balance. - From the dropdown menu, click `SAT (XML)`. - Open the generated XML file and inspect the `<BCE:Ctas>` nodes. **Observation:** - The generated XML uses the following attribute order: `Debe > NumCta > Haber > SaldoFin > SaldoIni` - However, the SAT-recommended structure is: `NumCta > SaldoIni > Debe > Haber > SaldoFin` **Root Cause:** At [1], the attributes of the `<BCE:Ctas>` node are defined in an order that differs from the SAT-recommended structure. While the XML remains valid, the generated report does not match the layout recommended by the Mexican government specification. **Fix:** This commit reorders the `<BCE:Ctas>` attributes to follow the SAT-recommended structure, aligning the generated XML with the behavior introduced at [2] for `saas-19.3`. backport-of: https://github.com/odoo/enterprise/pull/115374 [1]: https://github.com/odoo/enterprise/blob/cb9c19272309d793379fa4d23145162f72fa5552/l10n_mx_reports/data/templates/cfdibalance.xml#L15-L20 [2]: https://github.com/odoo/enterprise/blob/acf0929a88ec788aecd44f6b4c647e468dc0a319/l10n_mx_reports/data/templates/cfdibalance.xml#L17-L22 opw-6297711 Forward-Port-Of: odoo/enterprise#121440
The VAT field now shows a clearer placeholder to help users know what to enter when VAT does not apply. This reduces confusion and makes company and partner setup easier and more consistent.
Original PR description
Issue: - The placeholder on the VAT field is not proper - The user will be confused about what to write in the VAT field when it is not applicable Fix: - Update the placeholder on the VAT filed - '/' means VAT is not applicable Impact: - improve the user experience so that users know to write '/' when VAT is not applicable Task: 5005896
This update fixes an issue where pages could stretch wider than the screen and create unwanted horizontal scrolling. It improves how content fits on smaller or flexible layouts, making the interface more stable and easier to use without changing features.
Original PR description
Description of the issue/feature this PR addresses: **This PR addresses the horizontal scroll and layout responsiveness issues reported in [GitHub issue #222577](https://github.com/odoo/odoo/issues/222577).** - -Added overflow-x: hidden; to html, body, and #wrapwrap to prevent unwanted horizontal scrolling across the app. - Added max-width: 100%; and box-sizing: border-box; to the children of #wrapwrap to prevent content overflow. - Set width: 100%; and min-width: 0; on the main content section to ensure proper scaling and prevent flexbox overflow issues. - These are minor CSS/SCSS changes aimed at improving frontend layout behavior without breaking any existing features. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change adds an extra step to properly close a popover during automated testing. It prevents a rare cleanup error that could make test runs fail intermittently, improving overall reliability without changing user-facing behavior.
Original PR description
Add an extra step to close the popover and prevent the `Component is destroyed` error[1], which can happen during hoots cleanup, similar to the issue we see when some dialogs perform RPCs as they are being destroyed. [1]: https://runbot.odoo.com/runbot/build/115972540 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents a database error in the French PDP process when no start date is available. It makes the update logic handle missing dates safely, improving reliability for companies using this local feature.
Original PR description
Fixes _force_update_l10n_fr_f10_moves(). It would create a SQL query that compares a date to a bool when _pdp_get_flow_10_start_date() returned None.