Odoo Changelog — 2026-04-13

Monday, April 13, 2026

12 changes · saas-18.4

Bug Fixes(12)

Resolved issues and error corrections

### [FIX] spreadsheet: disable pivot grouping for unsupported field type

Coresaas-18.4spreadsheet

Spreadsheet pivots now avoid offering grouping on field types they cannot safely handle, such as JSON fields. This prevents crashes when users work with pivots and adds coverage to verify correct behavior across field types.

Original PR description

Spreadsheet pivots only do not support all field types. But we were
relying only on `field.groupable` to determine if a field could be
grouped, which is wrong (eg. JSON fields can be groupable but are not
supported). It leads to crashes for fields that were groupable,
but didn't have an entry in `pivotNormalizationValueRegistry`.

Added a test for all of the field types to ensure we have a correct
behavior.

Task: 6036075
Task: [6036075](https://www.odoo.com/odoo/2328/tasks/6036075)

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#255571

#spreadsheet#pivot#stability

[FIX] account: display product name in correct language in an invoice

PR #258707

Coresaas-18.4account

Invoice line product names now appear in the language of the specific invoice contact, even when that contact belongs to a parent company with a different language. This prevents customers from receiving invoices with product descriptions translated using the wrong contact language.

Original PR description

### Issue before this commit: When creating an invoice using the child contact of a parent contact that has a different language with respect to the father, the label of the invoice line was not…

### Steps to reproduce the issue:
1. Activate at least 2 languages (X and Y)
2. Create a product and set the translation for that product in the activated languages
3. Create a Contact with the language X
4. Create a child contact (invoice adress type) for that contact with language Y
5. Create a new invoice setting the customer as the child contact
6. Add the product you created
7. See the label is displayed in the language of the parent contact

### Cause of the issue:
The computation of the invoice line name relied on line.partner_id.lang. However, the partner_id of the move line is automatically set to the commercial partner that can be different (can be the father's contact) to the contact used on the invoice. As a result, the product description was translated using the wrong language.

### Reason to introduce the fix:
To ensure that invoice line labels are correctly translated according to the language of the selected invoice contact, the computation now uses the language of move_id.partner_id instead of line.partner_id. This guarantees consistent and expected behavior in multilingual environments, especially when using different contacts under the same commercial partner.

opw-5955875

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#258458
Forward-Port-Of: odoo/odoo#254833

[FIX] account: fix RTL brackets in invoice PDF

PR #258513

Coresaas-18.4account

Invoice PDFs now display parentheses correctly around Arabic product names, even when the invoice is printed in English. This prevents confusing or unprofessional-looking line descriptions for customers using mixed left-to-right and right-to-left text.

Original PR description

**Steps to reproduce:**
1. Create a product named: لوحة توزيع كهربائية 100 أمبير (شنايدر )
2. Create an invoice with that product
3. Print the invoice PDF in English
4. Observe the brackets are misplaced in the description column

**Current behavior:**
Parentheses appear detached from the Arabic word they enclose, floating at the wrong end of the text.

**Expected behavior:**
Parentheses correctly wrap the enclosed Arabic text.

**Cause of the issue:**
Odoo's report CSS sets `direction: ltr` on elements that are ancestors of the line description span. When CSS `direction: ltr` targets the same element as `dir="auto"`, wkhtmltopdf's WebKit engine lets the CSS rule win, keeping the paragraph base direction as LTR. The Unicode BiDi algorithm then resolves parentheses (neutral characters) using LTR as the base direction, misplacing them.

**Fix:**
Placing `dir="auto"` directly on the `<span>` that renders the line description — rather than the parent `<td>` — avoids the CSS override. wkhtmltopdf then detects the first strong character (Arabic) and uses RTL as the base direction for that span, allowing the BiDi algorithm to correctly position the brackets.

opw-5884712

Forward-Port-Of: odoo/odoo#257881
Forward-Port-Of: odoo/odoo#251190

[FIX] website: adjust color picker tabs for specific options

PR #249419

Coresaas-18.4website

The website editor now shows only the relevant color picker tabs for icons, snippet tabs, and scroll buttons. This removes a confusing Theme tab where it did not apply, making styling choices clearer for users editing website content.

Original PR description

This commit ensures the correct tabs are displayed in the color picker for Icon, Snippet Tabs and Scroll Button options.

The Theme tab was previously shown for these options, although it was not relevant in this context.

The color picker now only displays the tabs that make sense for each option.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#website editor#color picker#usability

[FIX] website: start countdown interaction in snippet preview dialog

PR #257480

Coresaas-18.4website

Countdown snippets now appear correctly when shown inside the website builder's custom snippet preview dialog. This helps users recognize and reuse saved snippets with countdown content without confusion.

Original PR description

The content of the countdown snippet did not appear in snippets preview dialog, because the interaction that fills it was not loaded for preview.

This commit adds the interaction in the registry for loading it inside the iframe of the snippets preview dialog.

Steps to reproduce:
- Open website builder
- Drop a `s_text_image` snippet
- Drop a `s_countdown` snippet inside
- Save the first one as a custom snippet
- Click on "Custom" snippets category
- Bug: the countdown does not appear

task-6088029

#website builder#snippets#preview#countdown

[FIX] sale: ensure negative discounts are not displayed in reports

PR #258888

Coresaas-18.4sale

Sales PDF reports now match the online customer preview by hiding negative discount values on order lines. This avoids confusing customers with discount figures that were not shown consistently across views.

Original PR description

Steps to produce:
---
- Install the `Sales` module.
- Enable discounts from settings.
- Create a Sale Order with a negative discount on an order line.
- Preview the Sale Order and click on the view details button.

Issue:
---
- Negative discount values are not shown in the preview (portal view), but they are displayed in the generated PDF.

Root cause:
---
- At [1], the portal template includes a condition to display discounts only when they are greater than 0, while the report templates lack this check, leading to inconsistent behavior.

Solution:
---
- Applied the same condition in the report templates to align the PDF output with the portal preview behavior.

Before:
---
<img width="787" height="136" alt="image" src="https://github.com/user-attachments/assets/d32311be-4aec-4d6f-b905-d5e52f712ba4" />

After:
---
<img width="775" height="139" alt="image" src="https://github.com/user-attachments/assets/2614a8ad-dca6-49ca-b720-5c234aa91cf6" />


[1]https://github.com/odoo/odoo/blob/0f463fd247d2f5da79d6ec2b6bec18774f6f600b/addons/sale/views/sale_portal_templates.xml#L539

Enterprise PR: https://github.com/odoo/enterprise/pull/111916

opw-6061568

Forward-Port-Of: odoo/odoo#258614
Forward-Port-Of: odoo/odoo#255735

[FIX] website: wait for the sidebar update before continuing test

PR #258876

Coresaas-18.4website

This update makes an automated website editor test wait until the sidebar is fully ready before checking its options. It helps reduce random test failures, supporting smoother validation and more reliable releases without changing customer-facing features.

Original PR description

In order to avoid undeterministic error, this commit fixes the test introduced by [1] by ensuring the sidebar is fully loaded before accessing options.

[1]: https://github.com/odoo/odoo/commit/137a6d7e59e1d788745c3b796a14839e52a8c5bc

task-6116678

#website#testing#reliability

[FIX] account_edi_ubl_cii: filter move without commercial partner to Export XML

PR #258944

Coresaas-18.4account_edi_ubl_cii

Confirmed accounting entries without a customer or vendor will no longer cause an error when users open the actions menu. The export option now skips entries that do not have the required partner information, keeping the workflow stable.

Original PR description

Issue:
Confirmed move without partner get a traceback while opening the cog wheel

Steps to reproduce:
- Create a misc move without Partner/commercial partner.
- Confirm it
- Click on the cog wheel button

Current behavior:
- Traceback

Before commit 48983eb6efdd6690f92f2839eedd39d9a288ab42, looping on `move.commercial_partner_id` prevented calling `_get_ubl_cii_edi_format` on empty records.

no-task

Forward-Port-Of: odoo/odoo#258881

#accounting#export#xml#stability

[FIX] hr_payroll: fix payslip warning bug

PR #112686

Enterprisesaas-18.4hr_payroll

This update fixes a misleading warning that appeared when employee contracts partially overlapped with payslip periods. The system now correctly handles overlapping contracts, preventing unnecessary alerts. This ensures smoother payroll processing and avoids potential user confusion.

Original PR description

[FIX] hr_payroll: fix payslip warning bug Bug reproduction: 1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well) 2 - Create an employee and make…

[FIX] hr_payroll: fix payslip warning bug

Bug reproduction:
    1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well)
    2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format.
    3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups.
    4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue.

Bug cause:
    1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing.
    2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear

Bug solution:
    1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period"

Tests:
    1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts.
    2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period)

Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well.

task - 6006693

Forward-Port-Of: odoo/enterprise#109791

[FIX] pos_blackbox_be: change price not working

PR #113329

Enterprisesaas-18.4pos

This update resolves a bug that prevented price changes in the POS system when using the Blackbox module and different decimal separators (like commas) based on the user's language settings. The fix ensures accurate price updates, improving the reliability of order calculations for all users.

Original PR description

Before this commit, when changing the price of an orderline with the blackbox installed, if the decimal separator of the user language was not a dot and was used during the price change, the price was not changed. This was due to the fact that we were comparing a string with a number, the string would be implicitly be converted to a number and, when there was a comma for example, it would return a NaN which would cause the discount to not be applied and thus the price to not change.

Forward-Port-Of: odoo/enterprise#113151

#POS#Blackbox#Price Calculation

[FIX] l10n_be_hr_payroll: Update FFE rates to 2026

PR #113638

Enterprisesaas-18.4l10n_be_hr_payroll

This update adjusts the FFE (Fonds voor Financiële Inlichtingen) rates used in the Belgian payroll calculations to reflect the latest figures for 2026. This ensures accurate payroll processing and compliance with Belgian tax regulations. The change is a technical fix to maintain current reporting.

Original PR description

Forward-Port-Of: odoo/enterprise#113426

#payroll#belgium#hr#finance

[FIX] hr_payroll: fix payslip warning bug

PR #113626

Enterprisesaas-18.4hr_payroll

This update resolves a warning message that appeared when generating payslips for employees with contracts that partially overlapped with the payslip period. The fix ensures that a warning only appears when there's a true overlap, aligning with the behavior in version 19. This improves the user experience and prevents unnecessary alerts.

Original PR description

Bug reproduction:
    1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well)
    2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format.
    3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups.
    4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue.

Bug cause:
    1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing.
    2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear

Bug solution:
    1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period"

Tests:
    1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts.
    2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period)

Last Test Update:
    1 - I noticed that contract date changes was not affecting the warning appearance directly
    2 - Unit test is expanded with contract date change and observing the warning appearance

Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well.

task - 6006693

Forward-Port-Of: odoo/enterprise#113566
Forward-Port-Of: odoo/enterprise#112758

Spreadsheet pivots only do not support all field types. But we were relying only on `field.groupable` to determine if a field could be grouped, which is wrong (eg. JSON fields can be groupable but are not supported). It leads to crashes for fields that were groupable, but didn't have an entry in `pivotNormalizationValueRegistry`. Added a test for all of the field types to ensure we have a correct behavior. Task: 6036075 Task: [6036075](https://www.odoo.com/odoo/2328/tasks/6036075) Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255571

### Issue before this commit: When creating an invoice using the child contact of a parent contact that has a different language with respect to the father, the label of the invoice line was not always displayed in the child contact language but in the father's contact language. ### Steps to reproduce the issue: 1. Activate at least 2 languages (X and Y) 2. Create a product and set the translation for that product in the activated languages 3. Create a Contact with the language X 4. Create a child contact (invoice adress type) for that contact with language Y 5. Create a new invoice setting the customer as the child contact 6. Add the product you created 7. See the label is displayed in the language of the parent contact ### Cause of the issue: The computation of the invoice line name relied on line.partner_id.lang. However, the partner_id of the move line is automatically set to the commercial partner that can be different (can be the father's contact) to the contact used on the invoice. As a result, the product description was translated using the wrong language. ### Reason to introduce the fix: To ensure that invoice line labels are correctly translated according to the language of the selected invoice contact, the computation now uses the language of move_id.partner_id instead of line.partner_id. This guarantees consistent and expected behavior in multilingual environments, especially when using different contacts under the same commercial partner. opw-5955875 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#258458 Forward-Port-Of: odoo/odoo#254833

**Problem:** When printing an invoice in English (LTR report) with a product whose name contains Arabic text and parentheses (e.g., لوحة توزيع كهربائية 100 أمبير (شنايدر )), the brackets appear in the wrong position in the generated PDF. **Steps to reproduce:** 1. Create a product named: لوحة توزيع كهربائية 100 أمبير (شنايدر ) 2. Create an invoice with that product 3. Print the invoice PDF in English 4. Observe the brackets are misplaced in the description column **Current behavior:** Parentheses appear detached from the Arabic word they enclose, floating at the wrong end of the text. **Expected behavior:** Parentheses correctly wrap the enclosed Arabic text. **Cause of the issue:** Odoo's report CSS sets `direction: ltr` on elements that are ancestors of the line description span. When CSS `direction: ltr` targets the same element as `dir="auto"`, wkhtmltopdf's WebKit engine lets the CSS rule win, keeping the paragraph base direction as LTR. The Unicode BiDi algorithm then resolves parentheses (neutral characters) using LTR as the base direction, misplacing them. **Fix:** Placing `dir="auto"` directly on the `<span>` that renders the line description — rather than the parent `<td>` — avoids the CSS override. wkhtmltopdf then detects the first strong character (Arabic) and uses RTL as the base direction for that span, allowing the BiDi algorithm to correctly position the brackets. opw-5884712 Forward-Port-Of: odoo/odoo#257881 Forward-Port-Of: odoo/odoo#251190

This commit ensures the correct tabs are displayed in the color picker for Icon, Snippet Tabs and Scroll Button options. The Theme tab was previously shown for these options, although it was not relevant in this context. The color picker now only displays the tabs that make sense for each option. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The content of the countdown snippet did not appear in snippets preview dialog, because the interaction that fills it was not loaded for preview. This commit adds the interaction in the registry for loading it inside the iframe of the snippets preview dialog. Steps to reproduce: - Open website builder - Drop a `s_text_image` snippet - Drop a `s_countdown` snippet inside - Save the first one as a custom snippet - Click on "Custom" snippets category - Bug: the countdown does not appear task-6088029

Steps to produce: --- - Install the `Sales` module. - Enable discounts from settings. - Create a Sale Order with a negative discount on an order line. - Preview the Sale Order and click on the view details button. Issue: --- - Negative discount values are not shown in the preview (portal view), but they are displayed in the generated PDF. Root cause: --- - At [1], the portal template includes a condition to display discounts only when they are greater than 0, while the report templates lack this check, leading to inconsistent behavior. Solution: --- - Applied the same condition in the report templates to align the PDF output with the portal preview behavior. Before: --- <img width="787" height="136" alt="image" src="https://github.com/user-attachments/assets/d32311be-4aec-4d6f-b905-d5e52f712ba4" /> After: --- <img width="775" height="139" alt="image" src="https://github.com/user-attachments/assets/2614a8ad-dca6-49ca-b720-5c234aa91cf6" /> [1]https://github.com/odoo/odoo/blob/0f463fd247d2f5da79d6ec2b6bec18774f6f600b/addons/sale/views/sale_portal_templates.xml#L539 Enterprise PR: https://github.com/odoo/enterprise/pull/111916 opw-6061568 Forward-Port-Of: odoo/odoo#258614 Forward-Port-Of: odoo/odoo#255735

In order to avoid undeterministic error, this commit fixes the test introduced by [1] by ensuring the sidebar is fully loaded before accessing options. [1]: https://github.com/odoo/odoo/commit/137a6d7e59e1d788745c3b796a14839e52a8c5bc task-6116678

Issue: Confirmed move without partner get a traceback while opening the cog wheel Steps to reproduce: - Create a misc move without Partner/commercial partner. - Confirm it - Click on the cog wheel button Current behavior: - Traceback Before commit 48983eb6efdd6690f92f2839eedd39d9a288ab42, looping on `move.commercial_partner_id` prevented calling `_get_ubl_cii_edi_format` on empty records. no-task Forward-Port-Of: odoo/odoo#258881

[FIX] hr_payroll: fix payslip warning bug Bug reproduction: 1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well) 2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format. 3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups. 4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue. Bug cause: 1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing. 2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear Bug solution: 1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period" Tests: 1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts. 2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period) Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well. task - 6006693 Forward-Port-Of: odoo/enterprise#109791

Before this commit, when changing the price of an orderline with the blackbox installed, if the decimal separator of the user language was not a dot and was used during the price change, the price was not changed. This was due to the fact that we were comparing a string with a number, the string would be implicitly be converted to a number and, when there was a comma for example, it would return a NaN which would cause the discount to not be applied and thus the price to not change. Forward-Port-Of: odoo/enterprise#113151

Bug reproduction: 1 - Select Hong Kong (actually there is nothing about Hong Kong, you can select other companies as well) 2 - Create an employee and make its contract from 01-01-2025 to 05-03-2026 (DD/MM/YYYY) format. 3 - Generate payslip for March, the warning of "The period selected does not match the contract validity period" popups. 4 - But we do not want that, even though there is 1 overlapping day in contract with payslip we can continue. Bug cause: 1 - In >= v.17 (not in v.19), there was a warning, when the contract dates do not fully contains the payslip dates, the warning was appearing. 2 - In v.19 it is not the case, when there is a contract that overlaps at least one dat of the payslip then we are fine, if no overlap then no contract on payslip warning should appear Bug solution: 1 - I replaced old warning "The period selected does not match the contract validity period" with the one in v.19 "No running contract over payslip period" Tests: 1 - There was a unit test about old warning (test_payslip_warnings), I changed that parts. 2 - I added further steps to the existing test about the new warning that should appear (No running contract over payslip period) Last Test Update: 1 - I noticed that contract date changes was not affecting the warning appearance directly 2 - Unit test is expanded with contract date change and observing the warning appearance Note: Implemented feature: need to check what happens after v.17, should be removed in v.19 latest, maybe before as well. task - 6006693 Forward-Port-Of: odoo/enterprise#113566 Forward-Port-Of: odoo/enterprise#112758