Monday, October 6, 2025
17 changes · master
Enhancements to existing features
The bank matching edit line wizard now shows only the line name, preventing long references from disrupting the layout. References remain available in the kanban view, so users keep access to the information without cluttering the edit screen.
Original PR description
Problem: - The reference field was displayed together with the bill name, causing misalignment when the reference is quite long in the edit line wizard. Solution: - Updated the edit line wizard to display only the line's name. - The reference remains visible in the kanban view, it is only removed in the edit line wizard. task-5113489 Forward-Port-Of: odoo/enterprise#95575
The website editor’s +New screen now shows the correct pictograms for content options instead of generic icons. This makes the interface more consistent with the newer Odoo visual style and easier for users to scan.
Original PR description
This PR adds missing icons to the +new screen interface. Requires : https://github.com/odoo/odoo/pull/136274 task-2941442 ### Introducing pictograms to the UI : Since we now have pictograms to represent the different purposes of a module across the backend, we replace the `fa-icons` with these pictograms. Most of these pictograms have already been added, but some were missing.
The IoT device screens no longer show the unused “last sent value” widget or a hidden IP field. The connection type is repositioned to make device forms more balanced and easier to read, especially for receipt printers.
Original PR description
This PR removes the "last sent value" widget from the iot device views + also removes the always invisible "iot ip" field + also moves the connection type to the 1st column of the view to avoid 2nd column being bigger than the 1st for devices like receipt printers. Odoo PR: https://github.com/odoo/odoo/pull/229918 Forward-Port-Of: odoo/enterprise#96276
This update aligns several automated tests with a newer testing behavior that preserves data more safely during expected error checks. It helps keep validation runs stable and reduces false failures without changing everyday user workflows.
Original PR description
See community change, now assertRaisesRegex uses savepoint by default. https://github.com/odoo/odoo/pull/229046
The field service project setup screen has been simplified by removing an unnecessary timesheet product field and its label. This reduces visual clutter and makes the interface clearer for users configuring field service sales workflows.
Original PR description
Remove the `timesheet_product_id` field from the view and hide its label to streamline the interface and improve clarity for users. task-4581748
The OdooFin bank connection flow has been cleaned up to make it easier to maintain. It also now refreshes currency information when connecting an existing account, helping prevent missing currency labels on account amounts.
Original PR description
The aim of this commit is applying a technical cleaning of OdooFin connector client action. This action exists since the beginning of Odoo Fin and in an effort of cleaning the enterprise module, this commit tries to clean the javascript code. This commit also adds a call to the reloadCurrencies function in the connect_existing_account case to make sure that we have potential newly activated currency in the session. Without that change, connecting to an existing account with a deactivated currency will lead to amounts without their currency. task-5107780
Resolved issues and error corrections
Rental product prices in the online shop now use the decimal precision configured for the website currency. This prevents public customers from seeing unnecessary decimals, such as showing whole-number currencies with two decimal places.
Original PR description
Versions -------- - 17.0 Steps ----- 1. Set currency precision to 0 decimals; 2. check prices in eCommerce as public user. Issue ----- Prices are displayed with 2 decimals Cause ----- The `_priceToStr` method used, always uses a `precision` of 2, except in editor mode when it will retrieve a different value from a hidden `.decimal_precision` element. Solution -------- Add the website's currency precision to `combination_info` via the controller, and use this value in `_priceToStr`. opw-4996878 Community PR: https://github.com/odoo/odoo/pull/224429 Forward-Port-Of: odoo/enterprise#96226 Forward-Port-Of: odoo/enterprise#95634
Odoo Studio now correctly handles clearing calendar view settings such as color fields. This prevents crashes when users remove these settings and keeps the calendar editor working smoothly.
Original PR description
On a calendar with studio, try to remove the "color" attribute, or any other that should contain the name of a field. Before this commit there was a crash because the value sent to the server in this case is `undefined` (`null` in JSON or `None` in python), which was stringified and yielding an actual string that was not a field name After this commit, NULL values are not stringified, instead they should represent the emptiness of the attribute. opw-4938351 Forward-Port-Of: odoo/enterprise#95439
This update adjusts how Studio approval rules are checked so they no longer trigger an unnecessary warning in newer database environments. It is an internal cleanup that helps keep system updates and migrations smoother without changing user-facing behavior.
Original PR description
See community change, merge `_method_or_action_not_null` into `_method_or_action_together` to avoid warning. https://github.com/odoo/odoo/pull/229287 https://github.com/odoo/upgrade/pull/8521
Fixed ESG demo data so it no longer depends on accounting records tied to a specific country setup. This prevents errors when loading demo data in fresh databases using non-US fiscal localizations, such as India.
Original PR description
**Note: issue not reproducible in runbot, but in fresh database** **Step to reproduce:** - in fresh database, install esg module - go to setting > invoicing > add india as Fiscal Localization -…
**Note: issue not reproducible in runbot, but in fresh database**
**Step to reproduce:**
- in fresh database, install esg module
- go to setting > invoicing > add india as Fiscal Localization
- change company name, ex "test"
- goto setting > load demo data
**Observation:**
- You will receive traceback
```
raise ParseError('while parsing %s:%s, somewhere inside\n%s' % (
odoo.tools.convert.ParseError: while parsing /home/odoo/odoo/codebase/enterprise/saas-18.4/esg/demo/demo_data.xml:567, somewhere inside
<record id="esg_emission_factor_line_assignation_4" model="esg.assignation.line">
<field name="esg_emission_factor_id" ref="esg_zero_emission_factor"/>
<field name="account_id" model="account.account" search="[('code', '=', '630000')]"/>
</record>
2025-09-11 08:45:07,458 82617 INFO esg184 odoo.addons.base.models.ir_module: module esg: no translation for language en_IN
2025-09-11 08:45:07,479 82617 ERROR esg184 odoo.sql_db: bad query: b'INSERT INTO "esg_activity_type_esg_emission_factor_rel" ("esg_emission_factor_id", "esg_activity_type_id") VALUES (1, 2) ON CONFLICT DO NOTHING'
ERROR: insert or update on table "esg_activity_type_esg_emission_factor_rel" violates foreign key constraint "esg_activity_type_esg_emission_fact_esg_emission_factor_id_fkey"
DETAIL: Key (esg_emission_factor_id)=(1) is not present in table "esg_emission_factor".
```
**Cause:**
- The demo data relies on few account.account record which belong to [USA company](https://github.com/odoo/odoo/blob/9805d09dff64de835de0c764da8c6e213d6b88aa/addons/account/data/template/account.account-generic_coa.csv#L38)
https://github.com/odoo/enterprise/blob/b8a20b02e27322d0db5781f8d84946e54bbcbf03/esg/demo/demo_data.xml#L569
https://github.com/odoo/enterprise/blob/b8a20b02e27322d0db5781f8d84946e54bbcbf03/esg/demo/demo_data.xml#L620-L628
- when we installed `india` Localization and changed the company name, USA company could not be created when loading demo data and hence the account records were not created, causing traceback
**Fix:**
- make demo data independent of any localization
opw-5048417
Forward-Port-Of: odoo/enterprise#94540Mexican electronic invoices will no longer automatically replace a missing invoice date with the current date in the Mexico City timezone when posted. This avoids unexpected mismatches between invoice and due dates and makes invoice behavior more consistent.
Original PR description
At the moment, when an invoice that uses a CFDI is posted, the invoice date (if not already existing) is set to the current date in the Mexico City timezone. This default behaviour is just weird, and even if there might have been technical reasons for it in the past, these are no longer valid. This can also cause the default invoice date to be different from the default due date, which causes unexpected behaviour in tests. We therefore remove this override. runbot-233041 Forward-Port-Of: odoo/enterprise#96303
The sales planning test tour was failing when run on non-working days because it focused on the current date. This fix changes the test so it selects only valid working dates, improving reliability of automated checks without changing user-facing behavior.
Original PR description
Before this commit, the tour was failing on non-working days as the focused day was the current date. This commit removes the focus on the current date so that only working dates are selected. Additionally, this commit also fixes the formatting issues of the modified file. runbot error 226741 Forward-Port-Of: odoo/enterprise#96239
A missing component was added back to the Spanish reporting setup after a forward-porting oversight. This helps ensure the related accounting return functionality is properly available when the module is initialized.
Original PR description
Little oopsie while fw-porting https://github.com/odoo/enterprise/pull/96106 Forward-Port-Of: odoo/enterprise#96354
Field service project settings now show the correct label for the timesheet product when a customer is selected. This prevents confusion caused by the sales order line label appearing in the wrong place.
Original PR description
Steps to reproduce: - Install the `industry_fsm_sale` module. - Open the FSM app. - Go to Projects. - Open a project’s settings. - Select a customer. Issue: The label for the timesheet product is not displayed. Instead, the label for the sale order line appears on FSM projects. Cause: In the PR, https://github.com/odoo/odoo/pull/128967 changed the project settings form structure by wrapping `sale_line_id` in a `div` and separating its label, breaking the xpath for `timesheet_product_id`. Fix: - Update the XPath for `timesheet_product_id` to target the correct container. - Hide the `sale_line_id` label on FSM projects. task-4581748 Forward-Port-Of: odoo/enterprise#96022
The Belgian 325 form PDF export now shows a helpful message instead of a server error when there are no 281.50 lines to include. This prevents a confusing crash and tells users what information is needed before exporting.
Original PR description
### Problem When clicking **"Export PDF"** on a 325 form that has **no generated 281.50 forms**, Odoo raised a **server error**: This happened because the method assumed that at least one attachment…
### Problem When clicking **"Export PDF"** on a 325 form that has **no generated 281.50 forms**, Odoo raised a **server error**: This happened because the method assumed that at least one attachment would always be generated, even if no eligible transactions were present. --- ### Steps to Reproduce 1. Go to **Accounting → Reporting → 325 Form**. 2. Create a 325 form for a year without any transactions on accounts tagged with **281.50**. 3. Do not generate any 281.50 forms (`form_281_50_ids` is empty). 4. Click **Export PDF**. **Result before fix:** - Crash with `IndexError: list index out of range`. --- ### Solution - Added a safeguard check before accessing attachments. - If no attachments exist, raise a **UserError** instead of crashing. **New behavior:** > *“No 281.50 lines found to generate a PDF. Please record a transaction with a 281.50 tag first.”* This gives users a instruction on how to resolve the issue. --- ### Result After Fix - **User error message** replaces traceback. - **Normal behavior preserved** when attachments exist: - One file → direct download. - Multiple files → zipped download. --- task-5090120 Forward-Port-Of: odoo/enterprise#94877
The payroll document generation process now skips payslips that cannot be linked to a valid employee contact. This prevents scheduled PDF generation from failing when an employee's related contact record has been deleted, keeping payroll document automation running smoothly.
Original PR description
Currently an error occurs when the **'Payroll: Generate pdfs'** scheduled action runs and tries to create a document for a payslip belonging to an employee who does not have a related partner.…
Currently an error occurs when the **'Payroll: Generate pdfs'** scheduled action runs and tries to create a document for a payslip belonging to an employee who does not have a related partner. **Prerequisites:** - Ensure HR is enabled in `settings>Documents` **Steps to Reproduce:** 1) Install `documents_hr_payroll` module.(with Demo) 2) Navigate to the Employees App. 3) Select any Employee(e.g Abigail Peterson) and open form view. >- click on **contacts** smart button. >- Delete that Record 4) Create a confirmed Payslip for the selected Employee(e.g Abigail Peterson). 5) Activate Developer mode and navigate to schedule Actions. >- Search for 'Payroll: Generate pdfs'. >- Run Manually. Error: `NotNullViolation: null value in column 'partner_id' of relation 'documents_access' violates not-null constraint` Root Cause: When the partner is deleted, the value received from `_get_document_partner` at [1] is `False`, which later on tries to create the `documents.access` record for the new document, it fails because no partner is available to assign access rights, resulting in the error. Solution: This commit prevent Error by ensuring `_check_create_documents` method doesn't allow document creation without valid partner. [1]: https://github.com/odoo/enterprise/blob/99a8d83edb42f172d0dd35c91743fa0c9653dcbb/documents_hr_payroll/models/hr_payslip.py#L20C1-L21 sentry-6814524392 Forward-Port-Of: odoo/enterprise#96191 Forward-Port-Of: odoo/enterprise#92865
This fixes how Odoo links exchange difference entries when multiple bank reconciliation lines are selected at once. It helps ensure the exchange adjustment is attached to the correct transaction line, reducing the risk of confusing or inaccurate reconciliation records.
Original PR description
When selecting multiple lines in the bank rec widget (reconcile button), it could happen that one of those lines have a exchange diff move linked to it. In this case, the exchange move id was placed on the first line all the time which could be wrong. This commit will change the use of indexes to use the reconciled line of the exchange diff move. no task id Forward-Port-Of: odoo/enterprise#95620 Forward-Port-Of: odoo/enterprise#94160