Saturday, March 7, 2026
4 changes · saas-19.1
Enhancements to existing features
This update enhances the demo data loading process in Odoo by ensuring the system accurately reflects demo module states and automatically installs demo modules. Previously, demo data didn't always update the system's state correctly. Now, the demo data loading is more reliable and consistent, providing a better starting point for users.
Original PR description
[IMP] core: improve force demo Improve the force demo function 1. update registry when demo data triggered module state changes 2. add ``install_demo`` to the context when loading demo data enterprise https://github.com/odoo/enterprise/pull/109792 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#250868
Resolved issues and error corrections
This update ensures that the 'Insert in spreadsheet' action is only visible to users with the necessary permissions for Documents and Dashboards. Previously, users without these permissions could still see the action, which has now been corrected for a more streamlined and secure user experience.
Original PR description
Current behavior before PR: - The 'Insert in spreadsheet' action was always visible in the list view action menu, even when the user lacked access rights for Documents or Dashboards. Desired behavior after PR is merged: - The action is shown in the list view action menu only if the user has the required permissions. Task: 5930184 Forward-Port-Of: odoo/enterprise#109739 Forward-Port-Of: odoo/enterprise#108099
This update resolves an issue that occurred when the demo version of Odoo Enterprise was used. Specifically, certain buttons were being triggered unnecessarily, causing unexpected behavior in the accounting module. This change ensures a smoother and more reliable experience for users in demo mode.
Original PR description
community https://github.com/odoo/enterprise/pull/97209 Forward-Port-Of: odoo/enterprise#109792
This update corrects a bug that prevented the system from accepting valid GSTINs for Non-Resident Indian (NRI) taxpayers. The previous validation rule was too restrictive, rejecting numbers that followed a different format. This change ensures accurate tax ID processing for NRI customers.
Original PR description
Currently, valid GSTINs for certain Non-Resident taxpayers are rejected. **Steps to reproduce:** - Install the `l10n_in` module. - Navigate to Settings > Users & Companies > Companies. - Open `IN…
Currently, valid GSTINs for certain Non-Resident taxpayers are rejected. **Steps to reproduce:** - Install the `l10n_in` module. - Navigate to Settings > Users & Companies > Companies. - Open `IN Company` and set `Tax ID` to `9922JPN29001OSU` and try to `save`. **Error:** `The VAT number [9922JPN29001OSU] for partner [IN Company] does not seem to be valid.` `Note: the expected format is 12AAAAA1234AAZA` The system rejects the GSTIN, although it is valid and verifiable on the official GST portal: https://services.gst.gov.in/services/searchtp **Root cause:** At [2], the GSTIN validation regex for NRI taxpayers only supports formats ending with `NRX` (X = any alphanumeric character). However, certain valid GSTINs follow a different structure and are not matched by the existing regex. **Fix:** This commit ensures that valid NRI GSTIN formats are accepted during validation. Confirm with IN PO. [1]: https://services.gst.gov.in/services/searchtp [2]: https://github.com/odoo/odoo/blob/5e59f4b3def44aa84c06ba4c2ed34bf2e8da928f/addons/base_vat/models/res_partner.py#L712-L723 opw-5956299 Forward-Port-Of: odoo/odoo#252647 Forward-Port-Of: odoo/odoo#251760