odoo/odoo#203896
Created by fw-bot
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:saas-18.1-16.0-microsoft_calendar-dont_sync_existing_events-gdpf-426178-fw
- head
- 0c041f2f7f8b00b1f5ed6bca0f1dfd333a3f110c
- merged
- 7 months ago by Fun Subscription - Sign - Cal, Gabriel de Paula Felix (gdpf)
| odoo/odoo | |
|---|---|
| 16.0 | #185911 |
| 17.0 | #199824 |
| saas-17.4 | #200957 |
| 18.0 | #203842 |
| saas-18.1 | #203896 |
| saas-18.2 | #203967 |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| master | #203979 |
[FW][IMP] microsoft_calendar: don't synchronize existing events
Before this commit, customers were facing problems during the first synchronization related to the abundance of invitations sent through Outlook from previously created events in Odoo side. This should not happen because most of the time it is not useful synchronizing events that were already created before starting the synchronization with Outlook (from feedbacks discussed with customers and internally).
After this commit, we no longer synchronize events that were created before the first synchronization of any user in a database if we don't find any token created in it (i.e. if no user synchronized its Odoo Calendar with Outlook before this improvement). In case of any user already have synchronized its calendar with Outlook, we won't change the synchronization behavior (since the biggest part of the invitations were already sent).