Thursday, January 8, 2026
3 changes · saas-18.2
Enhancements to existing features
This update adds crucial data attributes to Odoo's tax calculations and NFS-e submissions when the Brazilian fiscal reform is active. Specifically, the system now includes 'name', 'businessName', 'federalTaxId', and 'type' fields, ensuring accurate tax reporting and compliance with new regulations. This change improves the reliability of tax calculations for Brazilian businesses.
Original PR description
Purpose: Additional attributes are required to be sent in the rendered node for tax calculation and NFS-e submission when the fiscal reform is enabled. The additional required attributes are: - name - businessName - federalTaxId - type task-5450129 Forward-Port-Of: odoo/enterprise#103438
Resolved issues and error corrections
A recent update to the 'account_no_followup' module, automatically installed to support another module, triggered a memory error in existing Odoo databases with many accounting records. This fix avoids the memory issue by initializing the module's data directly in the database, preventing the error and ensuring smooth installations.
Original PR description
The module `account_no_followup` is a new module added in odoo/enterprise#96627. Since it's marked as `auto-install=True` and since it's a dependency of the new `pos_no_followup` module, it may be installed on existing 18.0 databases with a lot of account.move.lines. In this case, the module installation will raise a MemoryError as there's a new stored computed field on journal items called `no_followup`. Computing this field and storing the value in cache will overfill `self.env._cache` and reach the 2GB threshold. This commit fixes that by adding an overwrite of the `_auto_init` method to initialize the field's value in raw SQL, circumventing the issue. Forward-Port-Of: odoo/enterprise#102330
This update fixes a potential issue where applicants could incorrectly reopen expired or fully-signed job offers. The system now prevents access to these offers, ensuring data integrity and preventing any attempts to revert them to a partially signed state. A database constraint has also been added to ensure validity dates are always positive.
Original PR description
This commit improves the offer validation logic to avoid invalid or unintended signature attempts. Fixes included: - Block access to offers that are already fully signed, preventing applicants from reopening the link and unintentionally reverting the offer to a partially signed state. - Add an SQL constraint on the `validity` field to disallow negative values, ensuring that expired/invalid offers cannot be accessed due to incorrect validity data. These changes ensure that expired or fully processed offers no longer expose active signature links and that offer validity is consistently enforced at the database level. task-5405456 Forward-Port-Of: odoo/enterprise#103394 Forward-Port-Of: odoo/enterprise#101834