Friday, February 21, 2025
3 changes · 18.0
Enhancements to existing features
This update prevents errors caused by company-specific fields pointing to records that no longer exist. It improves reliability when loading or comparing these values, reducing unexpected disruptions for users working across companies.
Original PR description
When using JSONB for company-dependent many2one fields, references to non-existing records in the comodel can lead to MissingError. This commit introduces validation during fetch and comparison by taking advantage of index-only scan to ensure that referenced records exist. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Customer follow-up reports now use a dedicated statement format that focuses on the current year and only includes customer invoices. The report separates invoices that are due from those that are overdue, making payment follow-up clearer and less confusing for customers.
Original PR description
Instead of sending a confusing customer statement that includes invoices from the last period regardless of their status. Adding a new Partner ledger variant that will be sent as a follow-up report that provides the current year's customer statement including only customer invoices with separating Due and OverDue invoices. task-4454196
After pairing an IoT Box, users can now configure eligible devices for a selected Point of Sale directly from a popup. This reduces manual setup work for barcode scanners, customer displays, and receipt printers, making store onboarding quicker and easier.
Original PR description
To configure IoT Devices in a PoS we needed to pair the IoT Box, then go to PoS configuration and select devices (barcode scanner, customer display, receipt printer) one by one. We now display a popup right after IoT Box pairing, allowing autoconfiguration of eligible devices in the wanted PoS. Task: 4585446