Wednesday, April 15, 2026
5 changes · 18.0
Resolved issues and error corrections
This update ensures that the date range used to fetch transactions from iap is always accurate. Previously, incorrect dates could be used, leading to inaccurate data. Now, the system uses the latest statement or statement line date, prioritizing the lock date to guarantee correct transaction retrieval.
Original PR description
To fetch transactions from iap, we have to give a date from. Before this commit, it was possible to have a date from prior the lock date which is not supposed to happen. This commit will do the max between the lock date the last date of either the statement or the statement line. task-6019584
This update resolves an issue where a new document was repeatedly created when a user removed their Peppol journal. Previously, acknowledgements weren't sent, leading to a loop of duplicate document generation. This change ensures proper document handling and acknowledgement transmission, improving the reliability of Peppol integrations.
Original PR description
When a user removes its journal on its Peppol configuration, when receiving one, a new document would be created but the acknowledgement would never be sent to IAP. Everytime the user tries to retrieve new documents, the same document would then be created again.
This update addresses a regulatory requirement from the Mexican government (SAT) regarding CFDI payments. The system now prevents users from registering payments with future dates, eliminating the 'Update Payments' button when future payments are present. This ensures compliance and avoids potential issues with payment signing.
Original PR description
To sign a payment registered in the future is not allowed by the government. See http://omawww.sat.gob.mx/tramitesyservicios/Paginas/documentos/Guia_llenado_pagos.pdf Steps: - Create a PDD invoice (the due date should be at least 1 month later than the invoice date) - Send it to CFDI - Register a payment in the future -> We have the 'Update payments' button that appear on the invoice view, if you clik on it the payment will be signed With this commit, we filter out the payments with a future date, that way we don't have the 'Update Payments' button if there are only future payments, or the future payments won't be taken into account when clicking on the button. opw-5934753 Forward-Port-Of: odoo/enterprise#112320
This update fixes an issue where the table menu options weren't updating when the selected cell changed. The fix ensures that the menu accurately reflects the current target cell by updating values in real-time. This improves the user experience and data accuracy within the table editor.
Original PR description
After this commit [1], setup is executed only on the initial mount of the table menu and not on subsequent target cell changes. As a result, colItems, rowItems, and other values found in setup become stale, causing the menu to display options that do not reflect the current target cell. This commit moves the necessary values from setup into useEffect so they update correctly when the target cell changes. task-6111986 [1]: https://github.com/odoo/odoo/commit/7d523d6402c9bff3c2e4bcd0329f486a2d0f45ec Backport of Commit https://github.com/odoo/odoo/commit/729c45ddf3d1e377507d93997c5ca45984d64d75
This update resolves an issue where a Peppol document would repeatedly be created when a user removed their journal configuration. The fix ensures that acknowledgements are properly sent to IAP, preventing data duplication and improving the reliability of Peppol document processing. This ensures accurate data exchange and avoids unnecessary system load.
Original PR description
When a user removes its journal on its Peppol configuration, when receiving one, a new document would be created but the acknowledgement would never be sent to IAP. Everytime the user tries to retrieve new documents, the same document would then be created again.