Saturday, April 4, 2026
4 changes · saas-18.2
Resolved issues and error corrections
This update fixes a display issue in the Danish balance sheet and profit & loss reports, ensuring accurate reporting for Danish accounting practices. The changes simplify the report format and improve translation accuracy, aligning with Danish chart of accounts standards.
Original PR description
We updated the Danish balance sheet and profit and loss reports to reflect the changes in the Danish chart of accounts and common practice in Danish accounting. We also simplified the reports to use the accounts themselves as sublines instead of having a separate report line for each account. Finally we made sure we use the official Danish translations and updated the English translations as well. task-5929517 Related: https://github.com/odoo/odoo/pull/256541 Forward-Port-Of: odoo/enterprise#113001 Forward-Port-Of: odoo/enterprise#112430
This update resolves an issue where attempting to apply inactive TDS/TCS taxes in the Indian localization module would cause the system to crash. The fix allows the system to properly recognize and handle inactive taxes, preventing errors and improving system stability for users managing tax configurations.
Original PR description
Before this **PR**, attempting to apply an inactive tax resulted in a traceback. This occurred because l10n_in_section_tax_ids was empty, resulting in an empty iterable being passed to max(), which caused the error. To resolve this issue, l10n_in_section_tax_ids is now called with the context `active_test=False`. task-6074534 Forward-Port-Of: odoo/odoo#256809
Fixed an issue where the account balance for IAP (In-App Purchase) services would incorrectly reset to zero after saving a record, requiring users to manually refresh the page to see the actual balance. The balance now remains accurate immediately after saving.
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 resolves a problem where POS orders created in Jordan before installing the EDI module could not be submitted to JoFotara due to missing order identifiers. The system now automatically generates the required identifier when needed, ensuring all orders can be successfully submitted regardless of when they were created.
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