Thursday, June 6, 2024
3 changes · saas-17.1
Resolved issues and error corrections
A compatibility issue with the updated editor library caused QWeb profiling views to fail when displaying debug information. The fix changes where Odoo adds its extra information so the profiling view loads reliably again.
Original PR description
With the update of ace to 1.32.3, the lib is formatting her cells by getting them with hardcoded position in a array (here: 0, 1 and 2). On our side we are adding our o_info as first element, so the lib returns a traceback because her elements are shifted. After this commit, our info node is added after the lib nodes to not shift the all bunch. runbot issue 55085 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where opening Customer Invoices from a project's profitability updates could show a misleading “record not found” message. The project view now links to the correct customer invoice, helping users review project revenue without interruption.
Original PR description
Steps to reproduce: ------------------- - create a project - create an invoice with Analytic Distribution for the project - go to the project's updates - in profitability section, click on "Customer Invoices" Issue: ------ A notification appears: ``` It seems the record with ID X cannot be found. It might have been deleted. ``` Cause: ------ The arguments in JSON format are: ``` "["other_invoice_revenues", [["id", "in", [X]]], X]" ``` with X not corresponding to the invoice id. They are determined by the method `_get_action_for_profitability_section`. In which the ids are `invoices_move_lines.ids` (in `_get_revenues_items_from_invoices`). Solution: --------- Find the `account.move` from the `account.move.line`. Note: Introduced with the commit abd40a461c289bfe092784977077ceb1c7ef12f3 opw-3924836
Employment Hero payslip fetching now handles cases where a tax code is not configured in Odoo taxes. This prevents an unexpected error during payroll import and helps businesses continue processing payslips even when some tax mapping data is absent.
Original PR description
Steps to reproduce: - Run fetching payslip without provide the tax code in Odoo taxes Current behaviour: - Exception raised Expected behaviour: - Should not raise any exception Explanation: next() method is missing default value so it raised exception when filtering return empty array and iter() returns None. task-3897198