Odoo Changelog — 2026-05-04

Monday, May 4, 2026

3 changes · 17.0

Bug Fixes(3)

Resolved issues and error corrections

[FIX] helpdesk: prevent selecting customer from different company

PR #111909

Enterprise17.0helpdesk

This update corrects a bug where users could select customers from different companies within the Helpdesk system. The fix involved adding a restriction to the customer selection field, ensuring users only see customers within their assigned company. This improves data accuracy and prevents misdirected support tickets.

Original PR description

Steps to reproduce:
-

- Create two companies (Company A and Company B)
- Create one partner in each company
- Enable both companies for the user
- Open Helpdesk and go to the tickets Kanban view for a Company A team.
- In the quick create form, the customer dropdown shows customers from Company B

Issue:
-

 - Customers from other companies are visible in the customer field,

Cause:
-

 - The partner_id field in the quick create view had no domain, so it displayed partners from all allowed companies.

Solution:
-

 - Added a domain on partner_id in the Python field.

task-4971466

#helpdesk#customer selection#bug fix

[FIX] l10n_es_reports: show lines < 1 EUR in mod349 report

PR #114776

Enterprise17.0l10n_es_reports

This update corrects a bug in the Mod 349 tax report that prevented it from displaying vendor bills with amounts less than 1 Euro. The fix adjusts a calculation to ensure these small amounts are correctly included in the report, improving data accuracy for Spanish tax reporting.

Original PR description

Steps to reproduce:
- Install l10n_es_reports.
- Create a company from France.
- Create and post a vendor bill for that company with an amount of  0.12 EUR.
- Open the Tax Return report and switch to the Mod 349 report for the current year.
- Click the 0.12 EUR amount line.

Observed:
- The journal items view opens with no records.

Cause:
- `_get_modelo349_audit_aml_domain()` calls `_custom_modelo349_common()`, which filters lines using: `float_compare(result_dict['value'], 0, precision_rounding=2)`
- Using `precision_rounding=2` treats values below 1 as equal to 0, so those lines are excluded from the audit domain.

Fix:
- Replace `precision_rounding` with `precision_digits=2` so values are only treated as zero when they are effectively below 0.01.

opw-6134339

#reporting#tax#Spain

[FIX] pos_hr: recognize cashier with non "041" badge prefix

PR #262161

Core17.0pos_hr

This update resolves an issue where employees with manually created badges (without the '041' prefix) couldn't log into the Point of Sale system. The fix adds a fallback barcode listener to handle these cases, ensuring all employees can access the system. This was triggered by a mismatch between the system's barcode requirements and the badge format.

Original PR description

-> Error: "Unknonw Barcode: 1234567 ... The PoS couldn't find any product, customer, employee associated ...."

Why it's happening:
-------------------
The LoginScreen registers an exclusive barcode listener that only listens to barcode scan events related to employees, which makes sense on the login screen: we don't want to scan products or etc, just employees so they can log in.

However, from the nomenclature rules of point_of_sale, a cashier barcode must start with 041. Since our cashier has a custom barcode " 1234567" (not starting with "041"), the "cashier" barcode listener is never triggered, and a default error message is thrown.

Note that generating the badge with the "generate" button automatically appends the "041" prefix to the beggining of the badge code, so the issue does not exist if we automatically generate the badge.

Fix:
----
When the cashier barcode listener is registered from the login screen, i.e. with `exclusive === true`, we also add a fallback listerner on the 'product' type with the same cashier action! Why 'product'? Because it's the last type tried to match against, as last resort, when all the other types don't match.

With that fix, old employees having badges manually generated and hence not prefixed with "041" would be able to login.

opw-6125029

Steps to reproduce: - - Create two companies (Company A and Company B) - Create one partner in each company - Enable both companies for the user - Open Helpdesk and go to the tickets Kanban view for a Company A team. - In the quick create form, the customer dropdown shows customers from Company B Issue: - - Customers from other companies are visible in the customer field, Cause: - - The partner_id field in the quick create view had no domain, so it displayed partners from all allowed companies. Solution: - - Added a domain on partner_id in the Python field. task-4971466

Steps to reproduce: - Install l10n_es_reports. - Create a company from France. - Create and post a vendor bill for that company with an amount of 0.12 EUR. - Open the Tax Return report and switch to the Mod 349 report for the current year. - Click the 0.12 EUR amount line. Observed: - The journal items view opens with no records. Cause: - `_get_modelo349_audit_aml_domain()` calls `_custom_modelo349_common()`, which filters lines using: `float_compare(result_dict['value'], 0, precision_rounding=2)` - Using `precision_rounding=2` treats values below 1 as equal to 0, so those lines are excluded from the audit domain. Fix: - Replace `precision_rounding` with `precision_digits=2` so values are only treated as zero when they are effectively below 0.01. opw-6134339

Steps to reproduce: ------------------- 1. Create an employee, set its badge to "1234567". Don't generate the badge using the "generate" button, type it manually. 2. Print the badge of that employee, and take a photo of it for later. 3. Enable "Multi Employees per Session" for a PoS, and add the employee of step 1 into the "Basic rights" group. 4. Open the session, and click "Scan your badge", the camera will Open 5. Scan the badge printed in step 2 with the camera -> Error: "Unknonw Barcode: 1234567 ... The PoS couldn't find any product, customer, employee associated ...." Why it's happening: ------------------- The LoginScreen registers an exclusive barcode listener that only listens to barcode scan events related to employees, which makes sense on the login screen: we don't want to scan products or etc, just employees so they can log in. However, from the nomenclature rules of point_of_sale, a cashier barcode must start with 041. Since our cashier has a custom barcode " 1234567" (not starting with "041"), the "cashier" barcode listener is never triggered, and a default error message is thrown. Note that generating the badge with the "generate" button automatically appends the "041" prefix to the beggining of the badge code, so the issue does not exist if we automatically generate the badge. Fix: ---- When the cashier barcode listener is registered from the login screen, i.e. with `exclusive === true`, we also add a fallback listerner on the 'product' type with the same cashier action! Why 'product'? Because it's the last type tried to match against, as last resort, when all the other types don't match. With that fix, old employees having badges manually generated and hence not prefixed with "041" would be able to login. opw-6125029