Saturday, July 6, 2024
4 changes · master
Resolved issues and error corrections
This fixes an internal payroll accounting test related to employee leave allocation in Belgium. The change makes the test data setup more reliable by assigning values in an order that avoids accidental recalculation issues, helping keep payroll validation stable.
Original PR description
Given the definition of model hr.leave.allocation, assigning one field may lead to a recomputation fest, where sometimes a field looses its value. We simply changed the order in which fields are assigned.
This fixes an issue where changing tabs in a chart side panel could break the chart type dropdown. Users can now move between chart settings and design options without the dropdown failing.
Original PR description
The override would mistakenly reassign an object to `undefined`. How to reproduce: - Create a chart - open its sidepanel and go to the Design tab - go back to the Configuration tab - click on the cahrt type dropdown task-4032877
The appointment schedule now hides resources that are not linked to any appointment, preventing errors when users interact with the booking timeline. This keeps the resource booking view focused on relevant resources and avoids a traceback in normal scheduling workflows.
Original PR description
**How to reproduce:** - Make a new resource - Go to Schedule -> resource booking view (gantt by default) - Click on the timeline of newly created resource This gives a traceback. **Technical Reason:** - The case where resources has no appointment was not handled in the 'appointment_type_sync_duration.js' file. Handling this case with if statements. - The resources are displayed even though they are not attached to any of the appointment. Handling this by adding the domain. **After this PR:** - There will be no traceback on clicking the timeline of resources with no appointment (there will be no such resources due the domain). - Resources which are attached to atleast one of the appointments will only be displayed. Task-4000872
This fix prevents an error from appearing when users merge duplicate records in Data Cleaning. It corrects an internal reference so the merge action opens reliably after the module restructuring.
Original PR description
Cause: - This issue was caused after merging `data_merge` into `data_cleaning`. The external ID was not getting `data_merge_record_view_search_merge_action` because it is now in `data_cleaning`. this issue was introduced in this [PR](https://github.com/odoo/enterprise/pull/62979) Fix: - Corrected the module name in the external ID. task-4008186