Monday, March 10, 2025
4 changes · 18.0
Enhancements to existing features
This update lets Odoo recognize point-of-sale categories by their full hierarchy, so products can be imported into nested POS categories without errors. It improves data import reliability for businesses using multi-level POS category structures.
Original PR description
Description of the issue/feature this PR addresses: Adding new field for `_rec_name` (`complete_name`) which will be computed by hierarchy Current behavior before PR: Currently we cannot import product's POS category if it's nested. Odoo will show error because the POS category is not found Desired behavior after PR is merged: Will be able to import nested POS category --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Vendor bills are now checked more broadly for potential duplicates, including when dates are missing or only the same year matches. Suspected duplicates stay visible, are highlighted in list views, and prevent automatic posting so teams can review them before payment or accounting actions proceed.
Original PR description
See commits :) Entreprise PR: https://github.com/odoo/enterprise/pull/79471
Mexican localization now recognizes received vendor bills when checking SAT status, so users can see the SAT validation field on vendor bill forms. This brings vendor bill visibility closer to the existing invoice workflow and helps accounting teams verify compliance status more easily.
Original PR description
Adding 'invoice_received' as an accepted state in l10n_mx_edi_document.py -> _update_document_sat_state and account_move.py -> _compute_l10n_mx_edi_cfdi_state_and_attachment appears to be enough to enable the SAT functionality that is already present for invoices. With account_move SAT state no longer remaining None, the SAT field on the form view shows up by itself. Concern: adding 'invoice_received' state in l10n_mx_edi_document.py -> _create_update_invoice_document_from_invoice might also be needed to keep up the consistency, but I am not certain since that appears to go farther into CFDI-side logic. task-4368532
Potential duplicate vendor bills are now kept visible even after posting, including in list views. Automatic posting is stopped when a possible duplicate is detected, helping businesses avoid accidental duplicate payments.
Original PR description
Purpose ======= Recent changes have made bill encoding easier than ever (most notably, a bill date is set by default if left empty), but offering a robust duplicate bill detection is more important…
Purpose ======= Recent changes have made bill encoding easier than ever (most notably, a bill date is set by default if left empty), but offering a robust duplicate bill detection is more important than ever in the modern electronic invoicing world, where bills are more and more handled automatically. We want to make sure that: - Potential duplicates remain visible at all time, including in list view - Automated actions like auto posting are not done when a potential duplicate is detected. Specs ===== 1. Do not hide the warning on potential bill duplicate for posted invoices. The information remains pertinent. 2. When a move should be posted automatically (by the Auto-post feature on account.move or by the OCR auto-post), but a potential duplicate is found, prevent the auto-post from happening. Log the information in the chatter: "Auto-post was disabled on this invoice because a potential duplicate was detected." 3. In list view put the reference in red background when a potential duplicate on that invoice is detected. task-4578751 Community PR: https://github.com/odoo/odoo/pull/197891