Odoo Changelog — 2025-11-27

Thursday, November 27, 2025

4 changes · saas-18.2

Bug Fixes(4)

Resolved issues and error corrections

[FIX] l10n_mx_edi_pos: use partner CFDI usage

Enterprisesaas-18.2l10n_mx_edi_posMedium

This update ensures that Point of Sale orders in Mexico correctly utilize the customer's CFDI usage setting, rather than defaulting to 'G03'. This fix addresses a previous issue where the CFDI usage wasn't being applied, ensuring compliance with Mexican tax regulations for PoS transactions.

Original PR description

When making an order in the PoS in Mexico, if the customer has a CFDI usage set on their partner, it should be used for the order instead of the default one.

Steps to reproduce:
-------------------
* Install l10n_mx_edi_pos
* Create a partner with a CFDI usage different than 'G03'
* Open the PoS, select the partner and make an order
* Validate the order and check the order in the backend
> Observation: The CFDI usage is 'G03' instead of the one set on the
  partner.

opw-5018288

#Mexico#CFDI#POS#Tax Compliance

[FIX] l10n_be: Add company ID in attachment creation and move search domain.

PR #100676

Enterprisesaas-18.2l10n_beMedium

This update fixes an issue where documents and moves were incorrectly linked across companies in a multi-company setup. By explicitly including the company ID during attachment creation and searching, the system now accurately assigns documents to the correct company, preventing errors and ensuring data integrity. This improves the reliability of our multi-company accounting processes.

Original PR description

Behavior before:
In a multi-company setup, fetching documents could include records from different companies based on VAT numbers. When creating attachments or searching for existing moves, the company ID was not properly considered, leading to incorrect company assignments and failed move creation.

Behavior after:
Documents and moves are now created and searched within the correct company context by explicitly including the company ID.

Root Cause:
The company ID was missing in both the attachment creation and the domain used to search for existing moves, causing cross-company mismatches.

opw-4929985

Forward-Port-Of: odoo/enterprise#99192

#accounting#multi-company#VAT

[FIX] document: ensure control panel actions include all selected records

PR #100496

Enterprisesaas-18.2documentsMedium

Previously, the document control panel only processed the first 40 files selected, regardless of the total number uploaded. This update ensures that all selected documents are considered for actions like duplication or deletion, improving usability and data management. The fix addresses a limitation in how record selection was handled.

Original PR description

Steps to Reproduce
===================
1. Upload more than 40+ files in a folder. (One page displays upto 40 docs)
2. Use the checkbox to select all files on the page (this selects only 40 files)
3. Click the 'Select All' button in the control panel to select all 40+ files.
4. Now, try duplicating or moving them to the trash.
=> Only the first 40 selected files (on the single page) are considered for
   action, not all the selected files.

Technical
==========
For documents control panel action we have custom handling for selecting records
and executing action. We use `model.root.selection` which only consider records
in current page, case of select all records from other pages is missed here.

After this PR
==================
- All selected records are considered for the actions
- Added custom `getResIds` method to get filtered `resIds` as per domain.

Note: `getResIds` in DynamicList doesn't have custom domain feature so create
our own as per use case

Task-4700841

Forward-Port-Of: odoo/enterprise#87634

[IMP] sale_subscription: Dynamically fetch billing periods for portal

PR #100066

Enterprisesaas-18.2salesubscriptionMedium

This update fixes an issue where the customer portal wasn't correctly displaying daily subscription billing periods. The system now dynamically fetches billing periods from the subscription plan, ensuring accurate display and compatibility with custom subscription types. This improves the user experience and portal stability.

Original PR description

Problem -------- In v18.0, the day billing period was removed from the sale.subscription.plan model. For our use case, we require daily subscriptions, so we added this value back to the…

Problem
--------

In v18.0, the day billing period was removed from the sale.subscription.plan model.

For our use case, we require daily subscriptions, so we added this value back to the billing_period_unit selection field via inheritance.

However, this customization causes an error (a KeyError) when accessing the customer portal at /my/subscriptions/<int:order_id>. This is because the controller logic relies on a hardcoded list of periods and does not account for the new custom "day" value.

- Screenshot Order with plan Daily: 
<img width="1246" height="483" alt="image" src="https://github.com/user-attachments/assets/5dc5ca0d-a2f2-434d-8183-15a0424d9f34" />

- Screenshot when trying to get in order on the website: 
<img width="1250" height="776" alt="image" src="https://github.com/user-attachments/assets/5b10504e-71e2-4c13-8611-39e8a41e05d1" />


Proposed Solution
--------

This PR improves the subscription portal by dynamically retrieving billing periods instead of using a hardcoded list.

The portal now reads the available options directly from the billing_period_unit field's selection (i.e., self.env['sale.subscription.plan']._fields['billing_period_unit'].selection).

This improves maintainability, as future changes to the field's selection will be automatically reflected without requiring code modifications. This makes the portal robust and automatically compatible with any custom periods added via inheritance.

- 
<img width="1331" height="752" alt="image" src="https://github.com/user-attachments/assets/4f7be6c3-d96b-4525-8e23-6e1323adabde" />

Forward-Port-Of: odoo/enterprise#99207

When making an order in the PoS in Mexico, if the customer has a CFDI usage set on their partner, it should be used for the order instead of the default one. Steps to reproduce: ------------------- * Install l10n_mx_edi_pos * Create a partner with a CFDI usage different than 'G03' * Open the PoS, select the partner and make an order * Validate the order and check the order in the backend > Observation: The CFDI usage is 'G03' instead of the one set on the partner. opw-5018288

Behavior before: In a multi-company setup, fetching documents could include records from different companies based on VAT numbers. When creating attachments or searching for existing moves, the company ID was not properly considered, leading to incorrect company assignments and failed move creation. Behavior after: Documents and moves are now created and searched within the correct company context by explicitly including the company ID. Root Cause: The company ID was missing in both the attachment creation and the domain used to search for existing moves, causing cross-company mismatches. opw-4929985 Forward-Port-Of: odoo/enterprise#99192

Steps to Reproduce =================== 1. Upload more than 40+ files in a folder. (One page displays upto 40 docs) 2. Use the checkbox to select all files on the page (this selects only 40 files) 3. Click the 'Select All' button in the control panel to select all 40+ files. 4. Now, try duplicating or moving them to the trash. => Only the first 40 selected files (on the single page) are considered for action, not all the selected files. Technical ========== For documents control panel action we have custom handling for selecting records and executing action. We use `model.root.selection` which only consider records in current page, case of select all records from other pages is missed here. After this PR ================== - All selected records are considered for the actions - Added custom `getResIds` method to get filtered `resIds` as per domain. Note: `getResIds` in DynamicList doesn't have custom domain feature so create our own as per use case Task-4700841 Forward-Port-Of: odoo/enterprise#87634

Problem -------- In v18.0, the day billing period was removed from the sale.subscription.plan model. For our use case, we require daily subscriptions, so we added this value back to the billing_period_unit selection field via inheritance. However, this customization causes an error (a KeyError) when accessing the customer portal at /my/subscriptions/<int:order_id>. This is because the controller logic relies on a hardcoded list of periods and does not account for the new custom "day" value. - Screenshot Order with plan Daily: <img width="1246" height="483" alt="image" src="https://github.com/user-attachments/assets/5dc5ca0d-a2f2-434d-8183-15a0424d9f34" /> - Screenshot when trying to get in order on the website: <img width="1250" height="776" alt="image" src="https://github.com/user-attachments/assets/5b10504e-71e2-4c13-8611-39e8a41e05d1" /> Proposed Solution -------- This PR improves the subscription portal by dynamically retrieving billing periods instead of using a hardcoded list. The portal now reads the available options directly from the billing_period_unit field's selection (i.e., self.env['sale.subscription.plan']._fields['billing_period_unit'].selection). This improves maintainability, as future changes to the field's selection will be automatically reflected without requiring code modifications. This makes the portal robust and automatically compatible with any custom periods added via inheritance. - <img width="1331" height="752" alt="image" src="https://github.com/user-attachments/assets/4f7be6c3-d96b-4525-8e23-6e1323adabde" /> Forward-Port-Of: odoo/enterprise#99207