Sunday, September 27, 2026
2 changes · 17.0
Resolved issues and error corrections
This fixes an error that could occur when a Point of Sale order was paid using more than one payment method. The system now handles split payments correctly, preventing failures and allowing payment method information to display as expected.
Original PR description
ValueError: Expected singleton: pos.payment.method(1, 4) **Cause of the Error** The ValueError: Expected singleton: pos.payment.method(1, 4) error is raised in Odoo when an operation intended for a…
ValueError: Expected singleton: pos.payment.method(1, 4) **Cause of the Error** The ValueError: Expected singleton: pos.payment.method(1, 4) error is raised in Odoo when an operation intended for a single record (singleton) is instead applied to multiple records. In your code, pos_payment_ids is returning multiple payment methods for a single transaction because the customer has paid using multiple methods, like a mix of credit card, cash, and bank payments. When you try to access pos_payment.payment_method_id.name, Odoo expects pos_payment_ids to contain only one record, but here it has more than one (IDs 1 and 4, for example). This is common in cases where a customer splits the payment across multiple methods, resulting in several pos.payment.method records associated with the transaction. **Solution** To handle multiple payment methods, you can modify the code to process all payment methods associated with a transaction instead of assuming there's only one. You can join the names of each payment method into a single string, which can then be displayed in the widget. Here’s the updated code to address this: 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
Chile electronic invoicing now reuses each certificate's tax authority access token for the recommended 60-minute window. This avoids creating too many sessions after temporary connection issues, reducing the risk of rejected submissions for invoices, receipts, and stock documents.