Odoo Changelog — 2026-06-13

Saturday, June 13, 2026

2 changes · 18.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] account_edi_ubl_cii: skip UoM if from other category

Core18.0account_edi_ubl_cii

This update resolves an issue where UBL import failed due to a mismatch between the imported UoM category and the product's UoM category. The fix prevents automatic UoM setting in these cases, allowing users to easily correct the UoM after import. This ensures UBL invoices are successfully imported without disruption.

Original PR description

The new collected_values UBL import flow sets product_uom_id from the XML unitCode without checking that the resolved UoM category matches the matched product's UoM category. When they diverge, writing the line triggers the incompatible error.

Steps to reproduce:
- Create a product "XYZ" with UoM "Units" (category "Unit").
- Import a Peppol UBL bill whose line has Item/Name "XYZ" and unitCode="MTK" (uom_square_meter, "Surface").
- Import fails with: "The Unit of Measure (UoM) 'm²' you have selected for product 'XYZ', is incompatible with its category : Unit."

This fix will avoid setting the product_uom_id when the UoM category doesn't match the product's UoM category, allowing the line to be imported without error. The user can then manually set the correct UoM after import.

opw-6121714

#UBL#EDI#Import#UoM

[FIX] l10n_fr_pdp_pos: avoid access restriction on POS entries

PR #269815

Core18.0l10n_fr_pdp_pos

This update resolves an issue where accounting users were inadvertently accessing Point of Sale data due to a technical limitation in the PDP POS helper. The fix prevents access errors related to POS sessions, ensuring that accounting users only see data relevant to their roles. This improves data security and user experience.

Original PR description

Accounting users can access POS closing journal entries even when they do not have Point of Sale access rights.

The PDP POS helper checked POS session/order links directly while computing e-reporting fields on account moves. 
This could raise an access error on `pos.session` for accounting users without POS rights.

<img width="1621" height="728" alt="image" src="https://github.com/user-attachments/assets/fdee75b6-83f0-4d46-b8d1-e06d286447d3" />

#pos#accounting#reporting

The new collected_values UBL import flow sets product_uom_id from the XML unitCode without checking that the resolved UoM category matches the matched product's UoM category. When they diverge, writing the line triggers the incompatible error. Steps to reproduce: - Create a product "XYZ" with UoM "Units" (category "Unit"). - Import a Peppol UBL bill whose line has Item/Name "XYZ" and unitCode="MTK" (uom_square_meter, "Surface"). - Import fails with: "The Unit of Measure (UoM) 'm²' you have selected for product 'XYZ', is incompatible with its category : Unit." This fix will avoid setting the product_uom_id when the UoM category doesn't match the product's UoM category, allowing the line to be imported without error. The user can then manually set the correct UoM after import. opw-6121714

Accounting users can access POS closing journal entries even when they do not have Point of Sale access rights. The PDP POS helper checked POS session/order links directly while computing e-reporting fields on account moves. This could raise an access error on `pos.session` for accounting users without POS rights. <img width="1621" height="728" alt="image" src="https://github.com/user-attachments/assets/fdee75b6-83f0-4d46-b8d1-e06d286447d3" />