Odoo Changelog — 2025-11-12

Wednesday, November 12, 2025

3 changes · saas-18.2

Bug Fixes(3)

Resolved issues and error corrections

[FIX] documents: Allow users to drag and drop with touch devices

Enterprisesaas-18.2documentsMedium

This fix makes it possible to drag and drop documents on touch devices, where the previous browser behavior could lose the data needed to complete the drop. It improves the experience for mobile users by restoring a feature that was failing in some browsers.

Original PR description

For now, touch devices do not work with native drag and drop in browsers.
When a datatransfer is set on a dragstart event, it is lost before
reaching the drop event, but only when using a touch device.
Unfortunately, I still haven't found any sources that clearly explain
whether this is a known bug or a limitation.
The fact that on mobile (really mobile, not devtools, you need a touch
device) drag fails on Chrome but succeeds on Firefox.

To fix this issue, this commit manages datatransfers in an external
variable, without using the method in the Event.

I keep the original behavior as default, I just add a fallback to my
global datatransfer variable.

opw-5139435

Forward-Port-Of: odoo/enterprise#97091

#mobile#drag-and-drop#touch devices#documents

[FIX] sale_subscription: correctly update invoiced quantity for partial credit notes

PR #98892

Enterprisesaas-18.2sale_subscriptionMedium

This change fixes how subscription quantities are updated when an invoice is only partially credited. After the fix, the remaining invoiced quantity stays accurate instead of dropping to zero, which helps keep subscription billing records correct.

Original PR description

**Issue** When creating a partial credit note (i.e., for a quantity less than originally invoiced) for a subscription invoice, the `qty_invoiced` on the corresponding subscription order line is…

**Issue**
When creating a partial credit note (i.e., for a quantity less than originally invoiced) for a subscription invoice, the `qty_invoiced` on the corresponding subscription order line is incorrectly set to zero, instead of reflecting the remaining quantity.

**Steps to Reproduce**
1. Create a subscription with a quantity of 50.
2. Confirm the subscription and generate an invoice.
3. Create a credit note (reversal) for the invoice.
4. Change the credited quantity to 30.
5. Post the credit note.
6. The subscription order line shows qty_invoiced = 0 instead of the expected 20.

**Root Cause**
The method `_get_max_invoiced_date()` is used to determine the latest invoiced period for a subscription. In its original implementation, it removes refunded periods from the list of invoice dates regardless of whether the refund is partial or full. This causes the system to consider the period as not invoiced at all, which leads to incorrect recomputation of `qty_invoiced`

**Fix**
Adjust `_get_max_invoiced_date()` to track the net invoiced quantity per period. A period is only removed from the list of invoice dates if it has been fully refunded (i.e., net quantity is zero). This ensures that partially refunded periods are still considered invoiced, and the `qty_invoiced` is correctly updated to reflect the remaining quantity

Opw-4908760

Forward-Port-Of: odoo/enterprise#91344

[FIX] account_budget: access error with unrestricted analytic account

PR #99149

Enterprisesaas-18.2account_budgetMedium

This change prevents an access error that could appear when using the same unrestricted analytic account across multiple companies. It ensures purchase orders only check budget information the current user is allowed to read, avoiding interruptions for users working in company-specific budgets.

Original PR description

Steps to reproduce:
- Create an analytic account [ACCOUNT] not restricted to any company
- Create an analytical distribution model applying [ACCOUNT] to [PRODUCT] not restricted to any company
- Create a budget in company [COMP A] using analytic account [ACCOUNT]
- Create a budget in company [COMP B] using analytic account [ACCOUNT]
- In company [COMP B], create a purchase order, add [PRODUCT] to a line

Issue:

Access Error is raised

Analysis:

Because we search with sudo company rules are bypassed and the system
assign both budget lines to the order line (budget_line_ids).
When we access the field, the system try to access the budget line
of the other company, causing the error.

As solution we revert https://github.com/odoo-dev/enterprise/commit/4941c1928c9a2bcb38af3cadf023f904c9fd9be0
removing the `sudo` on the search and we explicitly check if the user
has read access on the budget analytic model

opw-5056712

Forward-Port-Of: odoo/enterprise#98573

#budget#purchase orders#multi-company

For now, touch devices do not work with native drag and drop in browsers. When a datatransfer is set on a dragstart event, it is lost before reaching the drop event, but only when using a touch device. Unfortunately, I still haven't found any sources that clearly explain whether this is a known bug or a limitation. The fact that on mobile (really mobile, not devtools, you need a touch device) drag fails on Chrome but succeeds on Firefox. To fix this issue, this commit manages datatransfers in an external variable, without using the method in the Event. I keep the original behavior as default, I just add a fallback to my global datatransfer variable. opw-5139435 Forward-Port-Of: odoo/enterprise#97091

**Issue** When creating a partial credit note (i.e., for a quantity less than originally invoiced) for a subscription invoice, the `qty_invoiced` on the corresponding subscription order line is incorrectly set to zero, instead of reflecting the remaining quantity. **Steps to Reproduce** 1. Create a subscription with a quantity of 50. 2. Confirm the subscription and generate an invoice. 3. Create a credit note (reversal) for the invoice. 4. Change the credited quantity to 30. 5. Post the credit note. 6. The subscription order line shows qty_invoiced = 0 instead of the expected 20. **Root Cause** The method `_get_max_invoiced_date()` is used to determine the latest invoiced period for a subscription. In its original implementation, it removes refunded periods from the list of invoice dates regardless of whether the refund is partial or full. This causes the system to consider the period as not invoiced at all, which leads to incorrect recomputation of `qty_invoiced` **Fix** Adjust `_get_max_invoiced_date()` to track the net invoiced quantity per period. A period is only removed from the list of invoice dates if it has been fully refunded (i.e., net quantity is zero). This ensures that partially refunded periods are still considered invoiced, and the `qty_invoiced` is correctly updated to reflect the remaining quantity Opw-4908760 Forward-Port-Of: odoo/enterprise#91344

Steps to reproduce: - Create an analytic account [ACCOUNT] not restricted to any company - Create an analytical distribution model applying [ACCOUNT] to [PRODUCT] not restricted to any company - Create a budget in company [COMP A] using analytic account [ACCOUNT] - Create a budget in company [COMP B] using analytic account [ACCOUNT] - In company [COMP B], create a purchase order, add [PRODUCT] to a line Issue: Access Error is raised Analysis: Because we search with sudo company rules are bypassed and the system assign both budget lines to the order line (budget_line_ids). When we access the field, the system try to access the budget line of the other company, causing the error. As solution we revert https://github.com/odoo-dev/enterprise/commit/4941c1928c9a2bcb38af3cadf023f904c9fd9be0 removing the `sudo` on the search and we explicitly check if the user has read access on the budget analytic model opw-5056712 Forward-Port-Of: odoo/enterprise#98573