Daily updates from Odoo
Saturday, January 10, 2026
4 changes · saas-18.3
Resolved issues and error corrections
This update fixes an issue where the Helpdesk return process incorrectly defaulted to internal 'PICK' operations instead of the final 'OUT' operations for multi-step deliveries. The fix ensures the correct customer-facing delivery order is selected, improving the accuracy of returns and streamlining the customer experience.
Original PR description
Steps to reproduce: - 1. Configure a warehouse for multi-step delivery (e.g., Pick + Ship). 2. Create a Sales Order for a product and fully process the delivery, including all steps. 3. Create a Helpdesk ticket for that customer. 4. From the ticket, click the "Return" button to open the wizard and select the sales order. Issue: - The return wizard incorrectly defaults to the first operation in the delivery chain (e.g., the internal 'PICK' operation) instead of the final, customer-facing 'OUT' operation. Cause: - Since picking is ordered by 'priority, scheduled_date asc, id desc', records are sorted by scheduled_date, this often resulted in selecting an internal 'PICK' operation instead of the final 'OUT' operation, making a more specific filter necessary. Fix: - The code now explicitly filters for pickings with the type code 'outgoing' and sets it as the default delivery order. task-4948134 Forward-Port-Of: odoo/enterprise#93154
This update automatically calculates and transmits the required 2050 retirement savings contributions (ELM) for Swiss companies using Odoo. Previously, this calculation was manual, introducing potential errors and delays. This change ensures accurate and timely reporting to the Swiss tax authorities, improving compliance.
Original PR description
task-5166226 Forward-Port-Of: odoo/enterprise#103542 Forward-Port-Of: odoo/enterprise#103453
This update clarifies error messages related to custom field access rules within Odoo. Previously, confusing error messages could hinder users from understanding why they lacked permission to view or modify certain fields. This change simplifies the messages, making it easier for users to resolve access issues and continue working efficiently.
Original PR description
Method `_check_field_access` may raise for fields that have no groups, in case there are custom field access rules. Simply make the details of the error message less confusing. backport of https://github.com/odoo/odoo/pull/231159 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 Forward-Port-Of: odoo/odoo#242856
This update fixes an issue where accepting UrbanPiper online orders in multiple POS locations resulted in multiple preparation tickets being printed. The fix ensures that preparation tickets are only generated once when an order is accepted, streamlining the order fulfillment process and reducing printing costs. It also removes local order records when an order is rejected.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103867 Forward-Port-Of: odoo/enterprise#100280