Saturday, September 21, 2024
6 changes · master
Resolved issues and error corrections
Manufacturing order cost summaries now show planned costs before production starts, begin actual costs at zero once work is in progress, and compare actual versus planned costs when finished. This helps teams better track production profitability and avoid misleading cost figures during manufacturing.
Original PR description
This PR contains small changes to adapt to the community PR. ------------------------ The mo overview costs are not accurate. Problems -------- - as soon as the MO is in progress, the real costs should start at 0, and the component cost should not be added untill they are consummed - when the MO is draft/confirmed, you should not see the real cost, but the bom cost to be able to compare it to what component are used/operations are planned on the MO - when the MO is done, you want to compare the real cost vs what was planned task-id: 3369946
Odoo now retrieves key invoicing authorization details directly from DIAN for Colombian electronic invoicing journals. This helps keep official numbering ranges, authorization dates, journal codes, and technical keys accurate, with a note added when values are updated.
Original PR description
Use GetNumberingRange to fetch the journal values: * l10n_co_edi_dian_authorization_number * l10n_co_edi_dian_authorization_date * l10n_co_edi_dian_authorization_end_date * l10n_co_edi_min_range_number * l10n_co_edi_max_range_number * code * l10n_co_dian_technical_key Log a message in the chatter if some fields are updated. task-4133688
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.
This fix prevents new bank connections from using an invalid default synchronization date when no lock date exists. It helps ensure first-time bank synchronization can start correctly and avoids provider errors during account setup.
Original PR description
Commit https://github.com/odoo/enterprise/commit/08a818bef6150c2877cdf64a7f4aa05ea14449e9 introduced a bug by setting journals last_sync to 1-1-1 when no lockdate is set. This would cause the first synchronization to fail because: - a start date would be set which is not wanted for first sync - the start date would be 1-1-1 which can cause error with some providers Reproduce bug: - Connect Saltedge Fake Bank OAuth with Pending Transactions - Select Account