Odoo Changelog — 2025-04-30

Wednesday, April 30, 2025

36 changes · saas-18.2

Bug Fixes(4)

Resolved issues and error corrections

[FIX] calendar: fix error when previewing a mail template

PR #204776

Coresaas-18.2calendar

Fixes an error that occurred when previewing the Calendar Attendee Information email template. Users can now preview this template normally, avoiding a disruptive traceback during email template setup or review.

Original PR description

When a user previews the mail template for Calendar Attendee Information,
A traceback will appear.

Steps to reproduce the error:
- Install ``calendar``
- Now go to Email Templates >
 Open email template (Applies to: ``Calendar Attendee Information``)
- Click Preview

Traceback:
```
File "/home/odoo/src/odoo/saas-18.2/addons/mail/models/models.py", line 300, in _message_get_default_recipients
    all_emails += defaults['partners'].mapped('email_normalized')
KeyError: 'partners'
```
https://github.com/odoo/odoo/blob/09099ab477bd871c67205388d96172280cd714a5/addons/mail/models/models.py#L300 Here, ``partners`` key is accessed but at [1] key is ``partner_ids``,
So, it will lead to the above traceback.

1-https://github.com/odoo/odoo/blob/09099ab477bd871c67205388d96172280cd714a5/addons/calendar/models/calendar_attendee.py#L116

sentry-6505820998

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

#calendar#email-templates#preview

[FIX] website_slides: prevent error when creating new attendees

PR #204264

Coresaas-18.2website_slides

Creating a new attendee from the eLearning reporting views no longer triggers an error when the new record has not been saved yet. This improves reliability for users managing course attendance and prevents an avoidable interruption in the workflow.

Original PR description

Currently, this exception is raised when a user tries to create a new attendee.

Steps to Reproduce:

1. Install `website_slides` module.
2. Go to eLearning ->Reporting -> Attendees
3. Switch to the Pivot view and click on a count integer.
4. Open the List View and click the "New" button.
5. An error Occurs

Error:
```SyntaxError
syntax error at or near ")"
LINE 18:             WHERE SCP.id IN ()
```

This issue[1] occurs because the system runs a query expecting an existing record with an ID, but since the record isn't saved yet, `self.ids` is empty, causing the query to fail.

[1]- https://github.com/odoo/odoo/blob/fbee52705e0332f7134eb5505eac26677e38c168/addons/website_slides/models/slide_channel.py#L91

This fix ensures that if self.ids is empty, the system stops the process early and sets a proper value, preventing the query from failing.

sentry-6465821899

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

#elearning#attendees#reporting

[FIX] mail: activity creation for x2m user field

PR #207453

Coresaas-18.2mail

Fixed an issue where automated actions creating activities could fail when a record had more than one user in a multi-user field. The system now creates the activity for the first user found, avoiding an error that blocked the action.

Original PR description

Have a server action that creates an activity based on a record's x2m user field.
Run that action on a record that has more than one user in this field.

Before this commit: display traceback "ValueError: Expected singleton"

After this commit: the activity is created for the first user found in the x2m field value.

Task id: opw-4745032

#activities#automation#user assignment

[FIX] base: ignore hidden/non-importable modules in `test_import`

PR #208067

Coresaas-18.2base

This fixes an internal test so it skips folders and items that are not meant to be imported as Python code. It helps developers run checks locally without false failures, improving confidence in routine maintenance.

Original PR description

The test was failing locally due to attempts to import non-Python modules like `.tx`, `.git`, and `odoo.setup`.

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

#testing#developer-experience#stability

Other(32)

Miscellaneous changes

[FW][FIX] hr_recruitment_integration_monster: missing dependency

PR #84540

Enterprisesaas-18.2

`hr_recruitment_integration_monster` bases one of its view overrides on `<setting id="job_board">`. This element is added by the `hr_recruitment_extract` module, but there is no dependency between the two. `hr_recruitment_integration_monster` only depends on `hr_recruitment_integration_base` which only depends on `hr_recruitment`. `hr_recruitment_extract` depends on `hr_recruitment` but also `iap`, `iap_mail`, and `mail_enterprise`. If any of these last 3 modules is uninstalled, `hr_recruitme

Original PR description

`hr_recruitment_integration_monster` bases one of its view overrides on `<setting id="job_board">`. This element is added by the `hr_recruitment_extract` module, but there is no dependency between the two. `hr_recruitment_integration_monster` only depends on `hr_recruitment_integration_base` which only depends on `hr_recruitment`.

`hr_recruitment_extract` depends on `hr_recruitment` but also `iap`, `iap_mail`, and `mail_enterprise`. If any of these last 3 modules is uninstalled, `hr_recruitment_extract` will be uninstalled and the `res_config_settings_view_form` view will explode the first time it gets resolved / validated.

Forward-Port-Of: odoo/enterprise#84491

When a user previews the mail template for Calendar Attendee Information, A traceback will appear. Steps to reproduce the error: - Install ``calendar`` - Now go to Email Templates > Open email template (Applies to: ``Calendar Attendee Information``) - Click Preview Traceback: ``` File "/home/odoo/src/odoo/saas-18.2/addons/mail/models/models.py", line 300, in _message_get_default_recipients all_emails += defaults['partners'].mapped('email_normalized') KeyError: 'partners' ``` https://github.com/odoo/odoo/blob/09099ab477bd871c67205388d96172280cd714a5/addons/mail/models/models.py#L300 Here, ``partners`` key is accessed but at [1] key is ``partner_ids``, So, it will lead to the above traceback. 1-https://github.com/odoo/odoo/blob/09099ab477bd871c67205388d96172280cd714a5/addons/calendar/models/calendar_attendee.py#L116 sentry-6505820998 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Currently, this exception is raised when a user tries to create a new attendee. Steps to Reproduce: 1. Install `website_slides` module. 2. Go to eLearning ->Reporting -> Attendees 3. Switch to the Pivot view and click on a count integer. 4. Open the List View and click the "New" button. 5. An error Occurs Error: ```SyntaxError syntax error at or near ")" LINE 18: WHERE SCP.id IN () ``` This issue[1] occurs because the system runs a query expecting an existing record with an ID, but since the record isn't saved yet, `self.ids` is empty, causing the query to fail. [1]- https://github.com/odoo/odoo/blob/fbee52705e0332f7134eb5505eac26677e38c168/addons/website_slides/models/slide_channel.py#L91 This fix ensures that if self.ids is empty, the system stops the process early and sets a proper value, preventing the query from failing. sentry-6465821899 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Have a server action that creates an activity based on a record's x2m user field. Run that action on a record that has more than one user in this field. Before this commit: display traceback "ValueError: Expected singleton" After this commit: the activity is created for the first user found in the x2m field value. Task id: opw-4745032

The test was failing locally due to attempts to import non-Python modules like `.tx`, `.git`, and `odoo.setup`. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Some languages aren't available on Transifex for saas versions if we do not have a dedicated maintainer for the language or not enough of the language is translated, but they are available for major versoins. As of the time of this commit this included: - Azerbaijani (az), - Bulgarian (bg), - Croatian (hr), - Estonian (et), - Greek (el), - Hebrew (he), - Hungarian (hu), - Latvian (lv), - Mongolian (mn), - Persian (fa), - Portuguese (pt), - Romanian (ro), - Ukranian (uk) Therefore this commit pulls the current translations from the 18.0 transifex project for these languages. Note that pot file msgmerges were not applied since the end result would have been the same, missing terms from pot files won't have a translation in the po file + extra terms in the po file not in the pot won't be used. 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

**Current behavior:** With anglo saxon accounting and real-time valuation, purchasing a kit product with a BoM that has components whose costs add up to the exact price of the kit product and that is invoiced on ordered qty and has avg costing, then billing before receiving will prevent the reception from being validate-able. **Expected behavior:** Can validate **Steps to reproduce:** 1. Create a kit product with avg costing, invoiced on ordered qty, and a BoM with 2 components that have a cumulative cost equalling that of the final kit product 2. Make a purchase for it, invoice -> post 3. Try to validate the receipt -> can't due to attempted re-reconicilation **Cause of the issue:** When validating the receipt, we end up here: https://github.com/odoo/odoo/blob/c9ea75efb8e260d6bea5b777f4f950f106ffcfa5/addons/stock_account/models/stock_valuation_layer.py#L81-L90 And attempt to reconcile both the original kit product AML from corresponding to the purchase line as well as the AML for the component in the stock input account. But we only will capture 1 exploded component AML in each loop iteration, so the original kit product AML will not actually be set `reconciled = True`, so we will also add it to be reconciled again: https://github.com/odoo/odoo/blob/c9ea75efb8e260d6bea5b777f4f950f106ffcfa5/addons/stock_account/models/stock_valuation_layer.py#L90 The same thing happens in subsequent calls to `_stock_account_anglo_saxon_reconcile_valuation()`, except on a final call for the last component line- if the components' cumulative cost aligns with the total cost of the kit product (which it should) then the reconciliation attempt will succeed. Then here: https://github.com/odoo/odoo/blob/c9ea75efb8e260d6bea5b777f4f950f106ffcfa5/addons/stock_account/models/stock_valuation_layer.py#L92 `reconcile()` is called on the already-reconciled AML which will cause the re-reconiliation error. **Fix** Reconcile all the resulting kit AMLs (component AMLs + actual kit product AML from the bill) together. opw-4668004 Forward-Port-Of: odoo/odoo#207803 Forward-Port-Of: odoo/odoo#205401

When using an intermediate return location, the delivered qty of a returned kit is incorrect To reproduce the issue: 1. In Settings, enable "Multi-Step Routes" 2. Create a location L: - Parent: WH - Type: Internal - Return location: True 3. Create a route: - Applicable on: Main warehouse - Add one rule: - Action: Push To - Operation Type: Internal - From: L - To: WH/Stock 4. Create a kit K 5. Sell and deliver 1 x K 6. Return it to L - It will create an internal transfer 7. Process the internal transfer 8. Open the SO Error: The delivered quantity of the kit is -1 instead of 0 Step 6, when returning the kit, the push rule is applied and create the SM from L to WH/Stock. Since we copy the SM from Customer to L, the new SM also has the field `sale_line_id` defined. As a result, step 7, since all SM are done, `moves` contain them (the delivery, the return and the internal transfer). We then filter them based on some criteria: https://github.com/odoo/odoo/blob/9918e8f3d627f3c52238d6b04bcd15c05d34e40c/addons/sale_mrp/models/sale_order_line.py#L67-L73 But, for `outgoing_moves` (which is actually the incoming ones, the name is wrong), since we look at the destination location, both the return and the internal SM will match. That's why we will decrease twice the delivered quantity. Hence, the bug. A fix could be to avoid copying the `sale_line_id` field. That being said, when looking `sale_stock` side (i.e., same flow with a classic product), we don't have any issue because the filters are slightly different: https://github.com/odoo/odoo/blob/418dc0cc3b3aa1ee2abbdb4852d9cd24fba7636e/addons/sale_stock/models/sale_order_line.py#L274-L278 (Here, we need to look at the `incoming_moves`. Again: the name is just incorrect on mrp side...) We see that, for `incoming_moves`, we actually look at the source location. This explains why we don't have any issue with a non-kit product. Therefore, the best fix would be to use the same filters everywhere. Good news, such a method already exist: https://github.com/odoo/odoo/blob/9918e8f3d627f3c52238d6b04bcd15c05d34e40c/addons/sale_mrp/models/sale_order_line.py#L115-L116 However, using this method might lead to some other issues (among them: the override in `sale_subscription_stock` reads a field although the method is an `api.model` one). So, let's minimize the diff on stable version and refactor the code (use the same filters everywhere) on master. About the filter names, the confusion actually comes from: https://github.com/odoo/odoo/blob/312572c7b8138a4800350cd7a524a37551a348ef/addons/mrp/models/stock_move.py#L624 There, we should rather talk about positive moves and negatives moves, since this method can be used either in a SO flow or in a PO one. This explains why, for now, SO sode, an "incoming move" is actually an outgoing one. So, on master, another commit will be added to also clean that part of the code: \- Improve the expected filter names in `_compute_kit_quantities` \- Fix the filter names in `_get_incoming_outgoing_moves_filter` OPW-4625228 Forward-Port-Of: odoo/odoo#207739 Forward-Port-Of: odoo/odoo#206966

Steps to reproduce [17.1]: - Add a property field to a job application in the backend. - Go to the linked website job application form (in edit mode). - The property field is inaccessible. To be able to access the new property field in the application form, the `job_id` value of the related job record needs to be specified by default. Unfortunately, these values are removed before accessing "edit" mode: Starting from [1], a fix was added to clear default values coming from `data-for` attributes when the form is edited (at `cleanForSave()`) to prevent saving it with changed default values. Since the code from [1] can also remove default values set by the user, a new fix (see [2]) updated this implementation to ensure that only values from auto-fill and data-for fields will be removed (this time, when the form public widget is destroyed [3]). The behaviour from [3] will always unlink the `data-for` values in edit mode, and as a consequence, the related property fields won't be correctly retrieved. The goal of this commit is to fix this behaviour by excluding `data-for` values from the reset in [3]. An extra check will be added to be sure the form won't be saved with updated default values if it already has `data-for` ones [4]. Important: The diff from [5] made the `email_to` field as an exception for the data-for/prefill priority system and only used the `data-for` value if nothing has been configured by the user (it also used the `data-for` value if what was configured by the user is the dummy default email: `info@yourcompany.example.com`). That's why we need to exceptionally allow saving the default value added by the user in the check from [4] to preserve the same behavior. Following [6], The `email_to` value won't be kept in edit mode to prevent breaking its dynamic behavior. [1]: https://github.com/odoo/odoo/commit/b637a5e32f767b62736241042f88fa0cecf9f10b [2]: https://github.com/odoo/odoo/commit/043e1fdf923d2037dd8da128ab99388f0c92e544 [5]: https://github.com/odoo/odoo/commit/a08574a04ff2ce8ea2d6fd2b79f56cc57bba953b [6]: https://github.com/odoo/odoo/commit/6658d61e304c9dfd8e512648c4a001dcaac44bc1 task-3922573 Forward-Port-Of: odoo/odoo#204027 Forward-Port-Of: odoo/odoo#166565

Bug Fixes(4)

[FIX] calendar: fix error when previewing a mail template

[FIX] website_slides: prevent error when creating new attendees

[FIX] mail: activity creation for x2m user field

[FIX] base: ignore hidden/non-importable modules in `test_import`

Other(32)

[FW][FIX] hr_recruitment_integration_monster: missing dependency

Bug Fixes(4)

[FIX] calendar: fix error when previewing a mail template

[FIX] website_slides: prevent error when creating new attendees

[FIX] mail: activity creation for x2m user field

[FIX] base: ignore hidden/non-importable modules in `test_import`

Other(32)

[FW][FIX] hr_recruitment_integration_monster: missing dependency

[FW][FIX] l10n_be_hr_payroll: termination report dates

[I18N] *: fw-port translations

[FW][FIX] pos_settle_due: customer statement button visibility

[FW][I18N] mrp_workorder: don't use `attribute` `add=""` to append string

[FW][FIX] l10n_be_hr_payroll: Upgrade to Dimona V2

[FW][FIX] hr_payroll: make report_payslip match payslip form

[FW][FIX] l10n_nl_reports: bad function name

[FW][FIX] account_reports: fix broken customer statements with cron

[FW] Saas 18.1 fix uom 2 abdu

[FW][FIX] web_studio: new model use company when in multicompany

[FW][FIX] account_reports: blank if zero affect total line

[FW][FIX] l10n_es_reports: MOD349 amounts with multi-installment payment …

[FW][FIX] hr_payroll: Salary attachments should only apply to input structure

[FW][FIX] test_module_operations: fix dbname configuration

[FW][FIX] test_lint: python 3.8 & 3.9 compatibility

[I18N] *: fw-port translations

[FW][IMP] hw_posbox_homepage: button to display/hide Wi-Fi password

[FW][FIX] stock_account: do not create unnecessary price difference when …

[FW][FIX] purchase_mrp,mrp_account: kit product bill then receive

[FW][FIX] test_website: fix website page properties tour

[FW][FIX] account: avoid computed account which is not allowed in journal

[FW][I18N] google_recaptcha: don't use `attribute` `add=""` to append string

[FW][FIX] sale_mrp: return kit in custom 2-steps

[FW][FIX] website: prevent the removal of the form's default values

[FW][FIX] point_of_sale: apply pricelist rules to the child categories

[FW][FIX] hr_recruitment: fix send email action

[FW] Saas 18.1 fix uom 2 abdu

[FW][FIX] l10n_it_edi: fix async multi-company send to SDI

[FW][FIX] packaging: avoid removing install dir

[FW][FIX] pos_loyalty: require pos_discount for global discount test

[FW][FIX] pos_self_order: pricelist not applied in kiosk