Saturday, March 29, 2025
5 changes · 18.0
Resolved issues and error corrections
Customer follow-up reminders now include the customer statement or follow-up report whether users choose print, email, or both. This prevents missing PDF content and ensures disabling invoice attachments no longer removes the required follow-up report.
Original PR description
Before, when sending a reminder for the followup via the send and print wizard, the customer statement, or the followup report, were only included if you checked email, but if only print was selected, the report was missing in the PDF. Now, when selecting print, email, or both, you get the report. opw-4570715
Miscellaneous changes
Currently, an error can occur in `_find_matching_po_and_inv_lines` when some invoice lines have a price_unit of 0. This happens because the matching logic sorts and matches lines by `(price_unit, qty)`, leading to "Journal Items" (`line_ids`) being incorrectly matched with purchase order lines. The issue arises because the `_find_matching_po_and_inv_lines` function checks all `line_ids`, instead of only `invoice_line_ids`. When a PO line has a price_unit of 0, it might match with a line that
Original PR description
Currently, an error can occur in `_find_matching_po_and_inv_lines` when some invoice lines have a price_unit of 0. This happens because the matching logic sorts and matches lines by `(price_unit,…
Currently, an error can occur in `_find_matching_po_and_inv_lines` when some invoice lines have a price_unit of 0. This happens because the matching logic sorts and matches lines by `(price_unit, qty)`, leading to "Journal Items" (`line_ids`) being incorrectly matched with purchase order lines. The issue arises because the `_find_matching_po_and_inv_lines` function checks all `line_ids`, instead of only `invoice_line_ids`. When a PO line has a price_unit of 0, it might match with a line that isn't an actual invoice line. As a result, `unmatched_lines` becomes incorrect, and it could remove a valid invoice line. Then, later, when calculating `inv_and_po_lines`, the process only considers `invoice_line_ids`. Since no matching line is found, an error occurs when attempting to delete the line (id is False). Steps to reproduce: 1. Create a purchase order with: - 1 product A with price_unit = 0 2. Confirm the purchase order. 3. Upload an EDI XML bill (e.g., IT localization) with: - A reference to the purchase order - 1 product B with price_unit = 100 Since all bill lines are processed, a tax line or a payment term line might incorrectly match with the PO line, causing the error. opw-4513869 Forward-Port-Of: odoo/odoo#197637
Ensure only Peppol-type proxies are retrieved when performing Peppol operations. Steps to reproduce: - Install Peppol and IT EDI - Register Peppol and IT EDI users - In Accounting, on the Vendor Bill journal, click "Fetch from Peppol" Odoo will attempt requests for all users, including an invalid call to 'False/api/peppol/1/get_all_documents'. This is not an issue in V17 but causes problems in V18. This fix makes sense in both versions as it prevents unnecessary requests a
Original PR description
Ensure only Peppol-type proxies are retrieved when performing Peppol operations. Steps to reproduce: - Install Peppol and IT EDI - Register Peppol and IT EDI users - In Accounting, on the Vendor Bill journal, click "Fetch from Peppol" Odoo will attempt requests for all users, including an invalid call to 'False/api/peppol/1/get_all_documents'. This is not an issue in V17 but causes problems in V18. This fix makes sense in both versions as it prevents unnecessary requests and avoids error messages in the logs. opw-4624633 Forward-Port-Of: odoo/odoo#203881 Forward-Port-Of: odoo/odoo#203734
With the new LIPE export, posting a closing entry opens an export wizard which breaks some tests. This PR implements a workaround to not open that wizard. --- Community PR: https://github.com/odoo/odoo/pull/195948 task-4507942 Forward-Port-Of: odoo/enterprise#80009
Original PR description
With the new LIPE export, posting a closing entry opens an export wizard which breaks some tests. This PR implements a workaround to not open that wizard. --- Community PR: https://github.com/odoo/odoo/pull/195948 task-4507942 Forward-Port-Of: odoo/enterprise#80009
Since 17.0, and before this commit, when the user navigates from an account report to another page and then comes back to the report through the breadcrumb, the user is brought to the top of the report. In 16.0, the user would be brought to the same position they were looking at. This commit brings this behavior back. task-4578468 Forward-Port-Of: odoo/enterprise#82072
Original PR description
Since 17.0, and before this commit, when the user navigates from an account report to another page and then comes back to the report through the breadcrumb, the user is brought to the top of the report. In 16.0, the user would be brought to the same position they were looking at. This commit brings this behavior back. task-4578468 Forward-Port-Of: odoo/enterprise#82072