Monday, February 17, 2025
5 changes · saas-17.4
Resolved issues and error corrections
This fixes an issue where Indonesian invoice emails and printed reports failed for non-admin users when QR code payment details were enabled. Accounting users can now send or print invoices without needing administrator permissions, while the restricted QRIS settings remain protected.
Original PR description
Problem: When a non-admin user tries to send an invoice by email or print an invoice report, an access error is thrown because the fields l10n_id_qris_api_key and l10n_id_qris_mid are locked behind the Admin/Settings group. Purpose: Non-admin users should be able to send and print invoices regardless of their admin rights. Apply sudo when accessing those specific fields. Steps to reproduce on Runbot: ADMIN 1. Install Contacts, Accounting, l10n_id 2. Enable QR Codes in Settings > Accounting 3. Give Marc Demo basic accounting and bank rights, but no admin rights MARC DEMO 1. Switch to ID Company 2. Create and confirm invoice 3. Attempt to send and/or print invoice 4. Access Error is thrown opw-4529074 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Incoming payments that require a partner bank account no longer need that bank account to be marked as approved for outgoing payments. This avoids confusion and fixes Ri.Ba. payment flows in Italy where money is received rather than sent.
Original PR description
The `require_partner_bank_account` flag on the payment shouldn't require the `allow_out_payment` flag on it when the payment type is `inbound` as it leads to confusion. This generates an issue with the `l10n_it_riba` Ri.Ba. payment method. It requires the bank account, but the money is incoming, not outgoing. Old PR for saas-17.2: odoo/odoo#195312 Enterprise PR: odoo/enterprise#78959 Task [link](https://www.odoo.com/odoo/project/967/tasks/4497749) task-4497749
This change ensures the delivery cost row is hidden only on the cart page, while remaining visible during checkout. This prevents checkout errors when customers switch to an available delivery method after an unavailable option is skipped.
Original PR description
The fix da95d25 introduced an issue in /checkout. Steps to reproduce: 1) Activate 2 delivery methods: one which fails and not available in /checkout and a valid one 2) Make sure the failed one comes first 3) Add a storable product to the cart, go to checkout 4) Observe that the delivery method is not chosen and delivery row in cart summary is not present 5) Select the available delivery method and observe the traceback Reason: Cart summary fails to update delivery row. After this PR: we will hide a delivery row only for the /cart page and show it for the others. opw-4397672
This fixes an issue where payment changes made after returning to the payment screen from the floor view were not saved in the backend. Businesses can rely on updated point-of-sale payment details being accurately reflected in records.
Original PR description
Before this commit: ========== - When the user returns to the payment screen from the floor screen and updates the payment line, the changes are not reflected in the backend. After this commit: ========== - Payment line changes will reflect in the backend after returning to the payment screen. task- 4512036
The barcode app now carries over a product's receipt or transfer description when staff create receipts or internal transfers. This keeps inventory documents complete and consistent, reducing confusion when reviewing draft operations outside the barcode workflow.
Original PR description
When creating a receipt or internal transfer using the barcode app, the description_picking field of the move_line is empty. Steps to reproduce the issue: - Create a product with a description for receipts (e.g., 'receipt'). - In the barcode app, create a new receipt and add the product (leave it in draft). - In the inventory app, check the corresponding receipt. The move_line has no description_picking, even though the product has one. opw-4406582 PR with a very similar issue: https://github.com/odoo/odoo/pull/193996