Daily updates from Odoo
Thursday, October 16, 2025
10 changes · master
Enhancements to existing features
Two sample invoice documents have been moved from the Taxes subfolder to the main Finance folder. This keeps demo content better organized and makes finance documents easier to find in the expected location.
Original PR description
Move two invoice demo files from the 'Taxes' subfolder to the parent 'Finance' folder. This makes more sense as they are not relevant to taxes. Task-5075610
The uninstall wizard now shows information about affected Studio customizations directly within the list of affected items instead of as a separate warning at the bottom. This makes the impact of uninstalling easier for users to understand before they proceed.
Original PR description
This commit builds upon https://github.com/odoo/odoo/pull/229087 to enhance the uninstall wizard UI related to Studio customizations. The warning alert previously shown at the bottom of the models list has been removed. Instead, information about affected customizations is now displayed as an additional item within the list of affected elements. task-5111398
The Rental Order button in the project topbar has been moved lower in the button order. This creates space for another related action to appear between Sales Orders and Rental Orders, making the topbar organization more flexible.
Original PR description
This commit alters the sequence set on the Rental Order embedded action to be able to put a new embedded action between Sales Order and Rental Orders ones in the project topbar. task-5164352
Shared project Gantt charts now group tasks by their title instead of by stage. This makes it easier for users to quickly identify and follow individual tasks in shared project views.
Original PR description
Before this PR: --- The Gantt view in project sharing was grouped by stage, which made it difficult to visualize tasks directly by their titles. After this PR: --- The Gantt view in project sharing is now grouped by title, improving clarity for shared projects. task-5138906
Resolved issues and error corrections
This fixes how Odoo Studio identifies the original view structure when simplifying customized screens. It helps prevent incorrect Studio view processing in cases where an inherited view is also treated as a main view, improving reliability for affected customizations.
Original PR description
Since commit 52f27c457e50a61c3b11c59e3fdd5ddd383f1317, the normalize function applies on `self` (ir.ui.view) and can take a string representing the arch to normalize. The normalization then occurs on the combination of the two, outputing a simplified version of the arch passed as a string in arguments. The base arch (`combined_arch`) is retrieved from self. Before this commit, this was done by controlling on self.inherit_id, which did not cover all bases to retrieve the main view's combined arch without the studio inheritance. After this commit, this is done by controlling on self.mode, because an inherited view can also be a root view. opw-5154217 Forward-Port-Of: odoo/enterprise#96992
This fixes a crash in Odoo Studio when users add a related monetary field on the same model, including its currency field. The change lets the Studio setup flow complete as expected, reducing disruption when customizing business screens.
Original PR description
In studio, add a related field to a monetary on the current model (ie without dotnames) Before this commit, it crashed. This because of c57c247490f0f58c8746af47ce035c28137faf97 After this commit, the flow works as expected opw-5147572 Forward-Port-Of: odoo/enterprise#97214
This fix corrects how the Belgian reporting partner form is linked so the required citizen identification field can be found during module updates. It prevents update failures and server errors when installing or upgrading the Belgian reports functionality.
Original PR description
The citizen_identification field was added to the partner view in l10n_be_reports, but the form 281.50 view for this required field was incorrectly inheriting from the base partner view. That led to…
The citizen_identification field was added to the partner view in l10n_be_reports, but the form 281.50 view for this required field was incorrectly inheriting from the base partner view.
That led to a traceback when updating account_reports/l10n_be_reports modules:
```py
Odoo Server Error
Occured on 86642809-master-all.runbot135.odoo.com on model ir.module.module on 2025-08-11 14:04:32 GMT
Traceback (most recent call last):
------- A lot of calls ------
convert_xml_import(env, module, fp, idref, mode, noupdate)
File "/data/build/odoo/odoo/tools/convert.py", line 745, in convert_xml_import
obj.parse(doc.getroot())
File "/data/build/odoo/odoo/tools/convert.py", line 616, in parse
self._tag_root(de)
File "/data/build/odoo/odoo/tools/convert.py", line 559, in _tag_root
f(rec)
File "/data/build/odoo/odoo/tools/convert.py", line 570, in _tag_root
raise ParseError(msg) from None # Restart with "--log-handler odoo.tools.convert:DEBUG" for complete traceback
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
odoo.tools.convert.ParseError: while parsing /data/build/enterprise/account_followup/views/partner_view.xml:4
Error while parsing or validating view:
Element '<xpath expr="//field[@name='citizen_identification']">' cannot be located in parent view
View error context:
{'file': '/data/build/enterprise/account_followup/views/partner_view.xml',
'line': 1,
'name': 'res.partner.view.form',
'view': ir.ui.view(5824,),
'view.model': 'res.partner',
'view.parent': ir.ui.view(127,),
'xmlid': 'res_partner_view_form'}
```This fix updates access settings so Swiss payroll-related employee fields use the correct payroll user permissions. HR officers can now access employee records as expected, preventing related automated workflow failures.
Original PR description
Some fields on the version were still with the hr_user group where they should be payroll_user. This was causing some tour to fail when an HR officer tries to access an employee. Build error: https://runbot.odoo.com/odoo/runbot.build.error/233204 Forward-Port-Of: odoo/enterprise#97175 Forward-Port-Of: odoo/enterprise#97096
Features or functions removed from Odoo
The WhatsApp module no longer includes demo data that conflicted with test data and did not provide useful business value. This helps keep testing and sample setups cleaner and reduces avoidable errors in demo environments.
Original PR description
Conflicts with test data, and according to tde these demo data make no sense as they do nothing useful. Closes #86194 https://runbot.odoo.com/odoo/error/223071 Forward-Port-Of: odoo/enterprise#97138
Code cleanup and technical improvements
Enterprise modules were updated to work with a related platform change where currency rate lookups now also include the rate date. This keeps reports, subscriptions, and localization documents aligned with the latest shared behavior without changing day-to-day workflows.
Original PR description
Now _get_rates() returns also the rate date. Change the enterprise usage. task-5109447 https://github.com/odoo/odoo/pull/228442 https://github.com/odoo/upgrade/pull/8593