3641000 - Appointment date reverts to original after update of the start and end date and performing sync using server side integration in C4C

Updating the start and end date of an older appointment in C4C reverts the date back to the original after saving and syncing using server side integration

SAP Cloud for Customer

1. Open an older appointment in C4C.
2. Change the start and end date from the older date to a date in the future.
3. Save the changes and sync using server-side integration.
4. Observe that the start and end date of the appointment revert back to the original after some time.

• The issue occurs due to a conflict during synchronization.
• The item was synchronized some time ago and fell out of the synchronization scope, but technical metadata remained intact on the Outlook side.
• When the start and end dates are updated in C4C, the reprocessing of the item is triggered. The Groupware ID is used to locate the corresponding item on the Exchange side.
• Two versions of the same event exist, one on each side, leading to a conflict. By default, the sync engine resolves the conflict by preferring the start and end date values from exchange.

1. This behavior is expected as the Exchange side always wins during the conflict resolution process by default.
2. If necessary, tenant configuration can be adjusted so that C4C always wins in case of conflict. However, this adjustment may result in invitations being sent to attendees again.

• Refer to: Conflict Resolution in Server-Side Integration

Appointment sync issue, c4c appointment date conflict, exchange sync conflict, c4c date reverts, groupware id conflict, server-side integration, invisible crm sync, c4c exchange conflict resolution, appointment metadata sync, c4c outlook sync issue, start and end date reverts, change date , KBA , LOD-CRM-GW-SCC , Invisible CRM - Smart Cloud Connect Solution , Problem