Sunday, December 3, 2023
3 changes · master
Miscellaneous changes
with this improvement now user can select the currency Chinese Yuan Offshore (CNH) and use it. my solution just adds the currency to the res_currency_data.xml opw-3599124 Forward-Port-Of: odoo/odoo#144331
Original PR description
with this improvement now user can select the currency Chinese Yuan Offshore (CNH) and use it. my solution just adds the currency to the res_currency_data.xml opw-3599124 Forward-Port-Of: odoo/odoo#144331
Before this commit, when a user was invited to an event from an account outside Outlook (e.g. Google account), accepting the invitation in Outlook Calendar didn't send the 'accept' status to Odoo Calendar, and vice-versa. This problem was also happening with recurrent events accepted in Outlook, the events weren't being accepted in Odoo Calendar correctly. After this commit, both ways are fixed: accepting an event in Outlook Calendar or Odoo Calendar notifies the other calendar correctly. For
Original PR description
Before this commit, when a user was invited to an event from an account outside Outlook (e.g. Google account), accepting the invitation in Outlook Calendar didn't send the 'accept' status to Odoo Calendar, and vice-versa. This problem was also happening with recurrent events accepted in Outlook, the events weren't being accepted in Odoo Calendar correctly. After this commit, both ways are fixed: accepting an event in Outlook Calendar or Odoo Calendar notifies the other calendar correctly. For recurrent events, accepting them in Outlook Calendar also updates the events status to 'accept' in Odoo Calendar (reminder: due to a limitation in Outlook Calendar synchronization, when the synchronization is active recurrent events acceptance can only be done through Outlook). Task-id: 3290922 Forward-Port-Of: odoo/odoo#144288 Forward-Port-Of: odoo/odoo#135836
To reproduce ============ - on planning create task 1 from 08:00 to 09:00 - on same day create task 2 from 17:00 to 18:00 tasks will be ordered as follow: | DAY | |--------| | task 2 | | task 1 | Problem ======= when fetching records from server, we order them by `resId`, where we lost the chronological order Solution ======== reorder the recorders after parsing opw-3566735 Forward-Port-Of: odoo/enterprise#51967 Forward-Port-Of: odoo/enterprise#50040
Original PR description
To reproduce ============ - on planning create task 1 from 08:00 to 09:00 - on same day create task 2 from 17:00 to 18:00 tasks will be ordered as follow: | DAY | |--------| | task 2 | | task 1 | Problem ======= when fetching records from server, we order them by `resId`, where we lost the chronological order Solution ======== reorder the recorders after parsing opw-3566735 Forward-Port-Of: odoo/enterprise#51967 Forward-Port-Of: odoo/enterprise#50040