Tuesday, September 2, 2025
10 changes · 17.0
Enhancements to existing features
The demo Peppol incoming bill has been replaced with a clearer, more useful example. This helps users evaluating or demonstrating Peppol workflows see a better sample invoice when using demo mode.
Original PR description
Replace Peppol demo bill that you get when fetching incoming bills in demo peppol mode.
Resolved issues and error corrections
The e-waybill screen now shows errors and warnings with the correct colors, making urgent issues easier to distinguish from cautionary messages. This reduces confusion for users reviewing Indian e-waybill information and improves how access-related errors are handled.
Original PR description
Before: --- Error and warning colors were mismatched in the e-waybill view. In this commit: --- Fixed the e-waybill view to correctly display error messages - Errors now display in red (alert-danger) :red_square: - Warnings now display in yellow (alert-warning) :yellow_square: AccessError now handled correctly. --- task-5050937
Miscellaneous changes
After the switch to Weblate, we now only use the `.weblate.json` file instead of the previous `.tx/config` file. Meanwhile added a new entry that was still added to the `.tx/config`.
Original PR description
After the switch to Weblate, we now only use the `.weblate.json` file instead of the previous `.tx/config` file. Meanwhile added a new entry that was still added to the `.tx/config`.
The Spanish Modelo 130 report now uses a date selector that matches how the report is calculated. This prevents users from choosing a misleading date range and helps avoid confusion about which accounting entries are included.
Original PR description
Currently mod130 report is configured to compute from the beginning of the fiscal period, however the date filter widget is in range mode. This means that when a user open the report and select a date range, the entries will not be just in the selected range but span from the beginning of the fiscal year to the end of the range, creating confusion. We should disable filter date range, so the date widget allow to set an end date to the current period Enterprise PR: https://github.com/odoo/enterprise/pull/90044 opw-4933241
This update adds a supporting helper in the Accounting tax area to enable a related enterprise fix. It is a small internal change intended to improve reliability without changing day-to-day user workflows.
Original PR description
helper used in https://github.com/odoo/enterprise/pull/92556 opw-4976780
This fix prevents an error when a settings header does not include a label or linked field. It makes labels optional as intended, improving reliability for configuration screens without changing user workflows.
Original PR description
Before this commit, an error would occur if a header setting did not contain an attribute string or field. This was because the code tried to infer the label. However, the label should be optional. 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 organization chart now correctly identifies employees and managers when viewed from user, employee, or public employee forms. This prevents incorrect or missing details in the chart, making employee hierarchy information more reliable for HR users.
Original PR description
This update ensures that the correct employee and parent IDs are fetched depending on whether the widget is displayed in a `res.users`, `hr.employee` or `hr.employee.public` form. The `onWillStart` was removed since `useRecordObserver` is triggered in `onWillStart`, and both used to have the same logic. task-5039701 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds test coverage for Spain's Modelo 130 reporting module to help ensure the report continues to calculate and behave correctly. It reduces the risk of regressions in Spanish tax reporting without changing day-to-day user workflows.
Original PR description
opw-4933241
Documents can no longer trigger a crash when users try to link a file to a type of record that has no entries yet, such as vehicles in a new Fleet setup. Instead, the action is blocked safely, avoiding disruption for users working in Documents.
Original PR description
*= documents_fleet Currently, when user tries to link a document with a vehicle and if there is no vehicle exists an error is raised. **Steps to Reproduce:** 1) Install `documents_fleet`…
*= documents_fleet Currently, when user tries to link a document with a vehicle and if there is no vehicle exists an error is raised. **Steps to Reproduce:** 1) Install `documents_fleet` module(without Demo Data). 2) Open Documents App. 3) Upload a file in `Fleet` folder. 4) Select the uploaded file and click on `'Link to a vehicle'` button. Error: `ValueError: invalid literal for int() with base 10: 'False'` Root Cause: The `link_to_record` method attempts to find the first record of the target model to use as a default value when opening the linking wizard. If no records exist, the search returns an empty recordset, and accessing `.id` at [1], on it results in the value `False`. The code then incorrectly constructs a default reference string like `fleet.vehicle,False`. The wizard crashes when it tries to parse this string and convert the `False` part to an integer. Solution: This commit prevents error by ensuring that the user cannot link a document to a model without existing records. [1]- https://github.com/odoo/enterprise/blob/83640d21b2c31ed9d572c48e02a9aeea9eb1607b/documents/models/documents_workflow_rule.py#L113 sentry-6792079496
After the switch to Weblate, we now only use the `.weblate.json` file instead of the previous `.tx/config` file.
Original PR description
After the switch to Weblate, we now only use the `.weblate.json` file instead of the previous `.tx/config` file.