Thursday, November 7, 2024
4 changes · saas-17.4
Resolved issues and error corrections
A small formatting error in one of OdooBot's automated random replies has been corrected. This prevents the bot message from showing broken or unintended HTML text, improving the polish of chat interactions.
Original PR description
Wrong closed parentheses in html_escape causes one of the OdooBot random responses to be rendered incorrectly. 
This update adjusts an automated test so it works whether demo data is enabled or not. It prevents false build failures caused by the administrator account having a different display name in non-demo environments.
Original PR description
When we do not activate demo data, name of the administrator is Administrator and not Mitchell Admin. Because of that, test fails. This fix checks the username of administrator and generates assert texts based on that. [broken build errors](https://runbot.odoo.com/web#id=105350&menu_id=424&cids=1&action=573&model=runbot.build.error&view_type=form) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The tax report now avoids showing incorrect consistency warnings when grouped tax lines have no valid net value. This prevents false alerts for accounting users and keeps the report focused on real issues.
Original PR description
### Steps to reproduce: - Go in Accounting > Reporting > Tax Report - Select "Group By: Tax > Account" - A warning should appear on the tax lines ### Cause: In the consistency check the net value retrieved is an empty string so the calculation is done with a net_value of 0 and an error is detected. ### Solution: If the net_value retrieved is not valid, the consistency check is not done. opw-4263695
Duplicating a completed quality check no longer reuses the original check’s name or control date. This prevents duplicate identifiers and ensures each copied check receives the correct new sequence information.
Original PR description
The issue: When duplicating a quality check, the name and control_date fields were copied, resulting in duplicated values. How to reproduce the issue: -Create a quality check -Pass the quality check -Duplicate the quality check Explanation: The name and control_date fields were duplicated during the copy process, preventing the create method from assigning the next sequence number. opw-4197697