Daily updates from Odoo
Navigate
Branch
Monday, May 2, 2022
10 changes
Enhancements to existing features
Users can now delete pivot tables and list views from Documents spreadsheets when they are no longer needed. This helps keep spreadsheets cleaner and easier to manage by removing obsolete reporting elements directly from the interface.
Original PR description
Task 2714352
Documents spreadsheets gain a dashboard mode that presents spreadsheet-based information in a more focused, read-only-style experience for monitoring business data. The update also refreshes the underlying spreadsheet engine and simplifies older mode handling, improving reliability and maintainability.
Spreadsheet-specific assets are now excluded from the list of selectable documents when editing website media. This prevents users from accidentally choosing internal spreadsheet files that are not meant to be used as website media.
Original PR description
Before this commit the spreadsheet assets could be selected as documents when editing a media in the website builder. After this commit the spreadsheet-specific assets name pattern is registered to utils.js to filter them out from the selectable list. task-2799866
Resolved issues and error corrections
This update fixes spelling and wording mistakes in translated text across several Odoo Enterprise apps. It improves clarity and professionalism for users without changing business processes or functionality.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/89718
This fixes a payroll issue that prevented users from opening payslip records after a previous change. Payroll teams can once again access payslip details normally, avoiding disruption in payroll review and processing.
Original PR description
Since odoo/enterprise#25736 it was no longer possible to open the payslips.
Code cleanup and technical improvements
Several enterprise views were updated to stay compatible with related platform changes. This keeps dashboards, maps, cohorts, spreadsheets, timesheets, projects, and reporting screens aligned with the latest underlying view framework without changing their business purpose.
Original PR description
This commit update the way views are defined to work with the corresponding commit in community.
Miscellaneous changes
A small change to fix the license from LGPL-3 to OEEL-1 in enterprise modules. One in 15.0, a few others in later versions. Forward-Port-Of: odoo/enterprise#26774 Forward-Port-Of: odoo/enterprise#26601
Original PR description
A small change to fix the license from LGPL-3 to OEEL-1 in enterprise modules. One in 15.0, a few others in later versions. Forward-Port-Of: odoo/enterprise#26774 Forward-Port-Of: odoo/enterprise#26601
Add a check in 'AccountTestInvoicingCommon' to ensure that all tests using it are run in post_install. These tests cannot be run at install, thus they would be ignored and wouldn't run on the Runbot. Forward-Port-Of: odoo/enterprise#26691 Forward-Port-Of: odoo/enterprise#25779
Original PR description
Add a check in 'AccountTestInvoicingCommon' to ensure that all tests using it are run in post_install. These tests cannot be run at install, thus they would be ignored and wouldn't run on the Runbot. Forward-Port-Of: odoo/enterprise#26691 Forward-Port-Of: odoo/enterprise#25779
The difference between the reference_date and the last unique slot does not represent always the correct duration because of the datetime. Based on the hours, the delta between the two datetime could lead to a duration shorten by a day. For example, if the reference date and the last unique slot are less than 1 day apart, the appointment_duration_days was equal to 0. (reference_date = 1st January 14:00 and last_slot = 2nd January 09:00) This was leading to weird behaviour, where a slot
Original PR description
The difference between the reference_date and the last unique slot does not represent always the correct duration because of the datetime. Based on the hours, the delta between the two datetime could lead to a duration shorten by a day. For example, if the reference date and the last unique slot are less than 1 day apart, the appointment_duration_days was equal to 0. (reference_date = 1st January 14:00 and last_slot = 2nd January 09:00) This was leading to weird behaviour, where a slot already taken was still displayed in the availabilities. Indeed the appointment_duration_days would than be equal to 0 because the 'days' property of the time delta would be equal to 0. This didn't reflect the correct duration and was impacting the availabilities computation. task-2806736 Forward-Port-Of: odoo/enterprise#26721 Forward-Port-Of: odoo/enterprise#25749
Alongside the other localisation modules on https://www.transifex.com/odoo/odoo-15-l10n Forward-Port-Of: odoo/enterprise#26740 Forward-Port-Of: odoo/enterprise#26727
Original PR description
Alongside the other localisation modules on https://www.transifex.com/odoo/odoo-15-l10n Forward-Port-Of: odoo/enterprise#26740 Forward-Port-Of: odoo/enterprise#26727