Overview
When Aurea CRM appointments are synchronized with Exchange Online using Connector SE, CRM-side changes can appear to “revert” after sync if the corresponding Exchange appointment was merely opened (even with no edits). This occurs because Exchange Online updates the appointment’s last modified timestamp on open, and Connector SE resolves conflicts based on modification timestamps—so the Exchange item is treated as newer and can overwrite CRM changes.
This is expected behavior driven by Microsoft Exchange Online timestamp behavior combined with Connector SE design. There is no Connector SE setting to bypass this timestamp-based conflict logic, and switching to Microsoft Graph API does not prevent it.
Key Information
-
Symptom: CRM appointment updates are overwritten after synchronization when the same appointment is opened in Exchange Online (without making any content changes).
“Connector SE sync overwrites CRM appointments with data from Exchange after just opening the appointments in Exchange Online” - Root cause (Microsoft-controlled behavior): Exchange Online updates an appointment’s “last modified” timestamp when the item is opened, even if the user does not edit any fields.
- Connector SE conflict handling (by design): Connector SE uses modification timestamps to decide which side wins. If Exchange reports a newer timestamp, Connector SE treats the Exchange item as the latest source of truth and can overwrite CRM-side changes—even when the Exchange content appears unchanged.
- Not an Aurea CRM defect: This behavior is an inherent limitation caused by Exchange Online timestamp behavior plus Connector SE timestamp-based conflict resolution (expected behavior).
- Microsoft Graph API does not change the outcome: Graph exposes the same underlying Exchange Online modification metadata, so the overwrite scenario can still occur.
- No Connector SE toggle to ignore “last modified” updates on open: Connector SE does not provide a configuration option to bypass/alter timestamp-based conflict resolution.
- No interactive conflict prompt: Connector SE does not support user prompts to choose which version (CRM vs. Exchange) wins; implementing interactive conflict arbitration would require an enhancement request and architectural changes.
- No patch identified: No internal engineering fix or version-specific patch is available for this behavior.
Customer Impact
What you should do: Use process and configuration mitigations to reduce conflicts, because the overwrite behavior cannot be disabled in Connector SE.
How to confirm you are experiencing this specific limitation
- In Aurea CRM (e.g., CRMpad/CRMweb), modify a field on a synced appointment (commonly a text/body-like field).
- In Exchange Online, open the same appointment and close it without editing.
- Run/allow the next Connector SE synchronization cycle.
- Verify whether the CRM appointment field(s) revert/are overwritten by the Exchange version.
Mitigations / workarounds
-
Usage / process controls (recommended):
- Define a single system of record for appointment edits (either CRM or Exchange).
- Minimize opening CRM-synced appointments in Exchange Online where feasible, especially immediately after making CRM changes.
-
Field mapping adjustments (where business rules allow):
- If certain CRM fields (e.g., appointment body/text notes or sensitive CRM-only content) do not need to appear in Exchange, update Connector SE mappings to exclude those fields from synchronization.
- This reduces the impact of overwrites because Exchange cannot overwrite fields that are not synced.
-
Permissions / governance controls:
- Enforce business rules so edits happen in only one system.
- Limit who can edit appointments in Exchange Online (or in CRM) for connector-managed records, and align team practices to avoid near-simultaneous changes across systems.
Validation after mitigation
Repeat the confirmation steps above and verify one or more of the following outcomes:
- Excluded fields are no longer overwritten (because they no longer sync).
- Following “single system of record” practices prevents unexpected reversions.
- Conflicts are reduced when Exchange opening/editing patterns are minimized.
When to pursue an enhancement request
If the business requirement is interactive conflict prompts (“choose which version wins”) or more sophisticated conflict resolution than timestamps, this requires an enhancement request (not supported by current Connector SE design).
Frequently Asked Questions
- 1. How do I know this is the same issue and not a different sync bug?
- You can reproduce it when a CRM appointment change is overwritten after the Exchange appointment is only opened (no edits). The key indicator is that Exchange updates the item’s “last modified” timestamp on open, and Connector SE then treats Exchange as newer during conflict resolution.
- 2. Will switching Connector SE to Microsoft Graph API fix the overwrite behavior?
- No. Graph API still exposes the same underlying Exchange Online modification metadata. The overwrite behavior is driven by Exchange Online updating “last modified” on open and Connector SE using timestamps for conflict resolution.
- 3. Is there a Connector SE setting to ignore Exchange “last modified” updates that happen just by opening an item?
- No. There is no configuration option in Connector SE to bypass/alter the timestamp-based conflict resolution that causes this behavior.
- 4. What is the most practical mitigation if users must keep working in Exchange calendars?
- Use process controls and system-of-record rules (edit in one system), and consider excluding CRM-only/sensitive fields from synchronization mapping where feasible. This reduces the likelihood and impact of overwrites.
- 5. Can Connector SE show a prompt to let the user choose which version (CRM or Exchange) wins?
- No. Interactive conflict prompts/arbitration are not supported by Connector SE by design. Supporting this would require an enhancement request and significant design changes.
Priyanka Bhotika
Comments