You’re offline. This is a read only version of the page.
25
Hi all,
I have found an issue with the server side sync with Exchange. Maybe someone can explain what's happening and why. And how to turn it off, maybe.
We have users syncing their contacts with Exchange/Outlook and we now noticed that the sync results in a save-operation on the contact in CRM. Apparently, after a contact has been created in Exchange, Exchange udpates some fields (for most of them it's Company Name, Description, Owner, Status Reason) with the same values. This "change" is then sync'ed back to CRM. While the values remain unchanged, this has two unwanted side effects: first, the modification date is changed (and we have reports and processes that rely on the modification date. And second, setting the owner (even though it's the same value), causes some processes to start that are triggered by the owner change/"Assign" operation.
Does anyone have an idea how we can prevent this from happening? We do want of course the two-way-sync - but this behaviour is very irritating.
Another thing we noticed: apparently Exchange can't handle addresses very well, where Street 2 is filled, but Street 1 isn't (I do not know exactly where these records come from, but unfortunately they exist.)
Thanks!
- Modified date
If you have to sync Contact, it is inevitable behavior. Because the values are newly updated on Exchange, even if the values are the same.
- Owner
It looks strange that the behavior of updating the owner value.
I encourage you to submit a Support Request to Microsoft to ask what the expected behavior is.
Share
Report
All responses (
Answers (
