Tuesday, October 3, 2023
4 changes · master
Resolved issues and error corrections
This fix makes exchange difference entries use the correct accounting date when payments or invoices are reconciled. It keeps reconciliation behavior consistent with unreconciliation, helping financial reports reflect currency gains or losses in the right period.
Original PR description
We align how the date is computed on exchange differences on how it already works when unreconciling. See _get_accounting_date(). Task-id:3516687 Community: https://github.com/odoo/odoo/pull/136911
The consolidation report now prepares its custom column headers in the right step of the reporting process. This prevents crashes when users open reports that rely on custom consolidation columns, restoring reliable access to those reports.
Original PR description
6c570325dc64adba441c748d834cee2c0fe488b7 changed the way javascript handles options. They are now generated by a different RPC call than the lines. It is hence not possible anymore to assign option keys within the functions computing the lines (or more generally speaking, subfunctions called by _get_report_information). Because of that, the column_headers option key of the consolidation report was always computed with a standard value, causing the report's custom components to crash when trying to opening it.
Web Studio approval indicators now refresh when users move between records or save changes that affect which approvals apply. This prevents outdated approval thumbnails from being shown, helping users see the right approval status without manually refreshing.
Original PR description
This commit fixes two issues: - Have a button that has two approvals: one with a domain, the other without with the pager change record from one that has the two approvals, to the one that has only one (or vice versa). Before this change, the approvals thumbnails did not update - Same case, but save one record that did have only one approval to make it have two (or vice versa) Before this commit, the approvals thumbnails did not update. This change set corrects those two use cases, and technically adapts the approval_hook to the new relational model, with which the record is itself reactive, meaning that we don't always go through willUpdateProps, rather, we use useRecordObserver. opw-3498555 opw-3382099
The appointment calendar now shows the next available date correctly when a user's month is fully booked. This prevents customers from seeing an "Invalid DateTime" message, making the booking experience clearer and more reliable.
Original PR description
Steps to Reproduce =================== 1. Book the whole month of any user. 2. Now try to access the monthly view of the user from the front end. 3. There we can see the 'Invalid DateTime'. Technical ========== Changing fromJSDate() to fromISO() because fromJSDate() only takes date object as an argument but in our case it is a string so it shows like 'Invalid DateTime' on the UI side. This issue is coming after the refactoring of the moment to Luxon. Task-3510350