Saturday, September 21, 2024
3 changes
Resolved issues and error corrections
When an analytic budget is revised, the new revised budget now keeps the same budget type as the original. This prevents confusion and helps ensure budget reviews and reporting stay consistent.
Original PR description
Description of the issue this commit addresses: When revizing an analytic budget, the revized budget doesn't have the type of the initial budget. --- Desired behavior after this commit is merged: The revized budget has the type fo the initial budget. --- task-4190606
The update prevents a reporting check from failing when it encounters invalid or non-readable invoice data. This keeps related document and accounting workflows running instead of being interrupted by unexpected file content.
Original PR description
Previously, the method `_is_l10n_in_irn_json` encountered a `UnicodeDecodeError` when processing binary content in JSON format, causing the failure of tests such as `test_bridge_folder_workflow`, `test_workflow_create_misc_entry`, `test_move_document_unlink`, `test_bridge_account_sync_partner` in the `documents_account` module. To resolve this, exception handling has been enhanced to suppress both `JSONDecodeError` and `UnicodeDecodeError`, ensuring the method can safely handle invalid or non-UTF-8 encoded content without interrupting the workflow. Fixes: https://runbot.odoo.com/web#id=98061&view_type=form&model=runbot.build.error&menu_id=405
Clearing a lead's email or phone will no longer erase those details from the linked customer record. This prevents accidental loss of contact information used by other business documents, such as sales orders and support tickets.