Tuesday, October 28, 2025
4 changes · 17.0
Resolved issues and error corrections
The Generate Pricelist Report action no longer crashes when no pricelist has been created. Instead, users see a clear error message explaining that a pricelist is needed, helping them resolve the setup issue without technical support.
Original PR description
Description of the issue/feature this PR addresses: When triggering the “Generate Pricelist Report” server action, an OwlError occurred if no pricelist record was defined in the database. This happened because the code attempted to access ctx.selectedPricelist.id while the pricelist context was undefined. Current behavior before PR: The system raises an OwlError when clicking “Generate Pricelist Report” if no pricelist exists. The user cannot open the report without manually creating a pricelist first. Desired behavior after PR is merged: A check ensures that a valid pricelist exists before generating the report. If no pricelist is found, a user-friendly error message is shown instead of a crash. Prevents the undefined context error on the client side. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Sales pricelist report now checks whether a pricelist exists before opening. If none is available, users see a clear message instead of a system error, helping them understand what setup is needed.
Original PR description
Description of the issue/feature this PR addresses: When triggering the “Generate Pricelist Report” server action, an OwlError occurred if no pricelist record was defined in the database. This happened because the code attempted to access ctx.selectedPricelist.id while the pricelist context was undefined. Current behavior before PR: The system raises an OwlError when clicking “Generate Pricelist Report” if no pricelist exists. The user cannot open the report without manually creating a pricelist first. Desired behavior after PR is merged: A check ensures that a valid pricelist exists before generating the report. If no pricelist is found, a user-friendly error message is shown instead of a crash. Prevents the undefined context error on the client side. https://github.com/odoo/odoo/issues/180247 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A minor test setup issue was fixed in the Project Timesheets Holidays module. This helps ensure time off and public holiday calculations are validated using the right user context, reducing the risk of future regressions.
Original PR description
In the 'test_timesheet_time_off_including_public_holiday' test case, 'employee' was mistakenly passed to 'with_user'. This commit replaces 'employee' with 'user' for consistency. task-4809916
This change corrects how Peppol-related partner screens build on existing accounting views. It prevents upgrade-related errors when moving from Odoo 16.0 to 17.0 with the Peppol module backported, improving reliability without changing user-facing behavior.
Original PR description
Currently the following views inherit from `base.view_partner_tree`: - `res_partner_form_account_peppol` - `res_partner_view_tree` The views mentioned about contain xpath expressions based on the `ubl_cii_format` field. But the view in `base` does not include the field yet. It is added in module `account_edi_ubl_cii`. This commit changes the inheritance to be from the equivalent views in `account_edi_ubl_cii` instead. Otherwise there is an error in a test when upgrading from 16.0 to 17.0 with the backported `account_peppol` to 16.0. task-4925169