Saturday, April 4, 2026
3 changes · saas-18.3
Resolved issues and error corrections
Fixed an issue where the account balance in IAP (In-App Purchase) accounts would incorrectly reset to zero after saving a record. Users previously had to refresh the page to see the actual balance. Now the balance remains accurate immediately after saving, improving the user experience and reducing confusion.
Original PR description
Before this commit: When creating an `iap.account`, selecting a service(`service_id`) showed the correct balance. However, as soon as the record was saved, the balance would reset to 0, and users had to refresh the page to see the real value. With this fix, the balance now stays accurate after saving the record. Task [link](https://www.odoo.com/odoo/project.task/6004546) task-6004546 Forward-Port-Of: odoo/odoo#256589
This fix prevents files from becoming orphaned when an error occurs during file upload. Previously, if a file write operation failed (such as due to disk space issues), the system wouldn't clean up the incomplete file, causing storage waste and blocking future uploads of the same file. Now the system properly marks files for cleanup before attempting to write them, ensuring disk space is freed even when uploads fail.
Original PR description
If an error occurs during the file write operation, the file will not be marked for garbage collection, which can lead to orphaned files taking up disk space or blocking other same file to be written. Step to reproduce the issue: 1. Create an attachment with a large file (e.g., 100MB) and save 2. During the file write operation, simulate an IOError (e.g., by filling up the disk space or changing file permissions) 3. The file will not be marked for garbage collection, and it will remain 4. Further attempts to create this same attachment will result in error: "The attachment collides with an existing file." opw-6055037 opw-5907025 Forward-Port-Of: odoo/odoo#257384 Forward-Port-Of: odoo/odoo#257274
This fix resolves a problem where POS orders created in Jordan before installing the electronic invoicing module were failing to submit to JoFotara due to missing unique identifiers. The update ensures that order identifiers are automatically generated when needed, preventing submission errors and allowing these orders to be processed successfully.
Original PR description
Currently, POS orders in Jordan do not have a UUID if they were created before installing the module. This causes submission failures to JoFotara. Steps to reproduce: - Create a POS order in Jordan without the module l10n_jo_edi_pos installed - Install l10n_jo_edi_pos - Try to submit the order to JoFotara, it fails due to missing UUID with the error "Invoice UUID is required" This fix force a computation of the order UUID when we add the header node, to ensure that this will not cause submission failures to JoFotara. opw-6041688 Forward-Port-Of: odoo/odoo#255996