Birthdate change to one day in past with office 365 server-side-sync and dynamics 365 on-prem

(0) Share

Report

Posted on by LukeHendo

195

I have this strange issue that has appeared that I hope someone can help with

All of the contacts in dynamics 365 on-prem have had their birthdate changed to one day in the past. I have narrowed this doen to being related to the server-side-sync with office 365. When I turn sync off, birthdates of contacts that I add to dynamics remain correct (i.e. as I inputted them), however when I turn sync on, they are changed to the day before (this is in both office 365 and dynamics 365).

Does anyone have an idea as to how I can fix this? I feel it could be relateed to daylight savings, but not sure?

Thanks for your help!

Luke

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Suggested answer

BadrinathB 970 on at

Like (0)

Report

Hi Luke,

The Date Only format is designed to overcome the issue of different dates appearing for different people based on their time zone.

I will prefer Date Only format for the birth/death dates and GMT +00:00 for the users' time zone.

Try this if it works. If you are using the Microsoft CRM Outlook Client - the Time Zone setting will be automatically set for you based on your Windows Time Zone setting. Microsoft CRM will display the date respective to the Microsoft CRM User's Time Zone setting. If CRM User One (Pacific Time zone) created another CRM contact record at 11PM on April 22nd, that record's created date will be show as 2AM April 23rd (vs April 22nd) if viewed by CRM User Two (Eastern Time zone).

For more details related to DateTime issues

blogs.msdn.microsoft.com/.../datetime-values-in-microsoft-dynamics-crm

Was this reply helpful? Yes No
LukeHendo 195 on at

Like (0)

Report

Was this reply helpful? Yes No
LukeHendo 195 on at

Like (0)

Report

Thanks for your response. Unfortunately this does not appear to be the solution - I already have it set up as date only. The problem appears to be on the office 365 end, as the birthdate only changes after it has synced with office 365? Any other ideas?

All computers and servers associated with the dynamics 365 are set to the same time zone.

Thanks again for your help.

Luke

Was this reply helpful? Yes No
BadrinathB 970 on at

Like (0)

Report

Hi Luke,

Your CRM seems to be on-premise and office 365 is trying to overwrite the Birthadate when you switch on the Sync behavior. Could you please check the timezone set for office 365? below are the steps to verify.

support.office.com/.../change-your-display-language-and-time-zone-in-office-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b

Was this reply helpful? Yes No
LukeHendo 195 on at

Like (0)

Report

timezone is the same in office 365.

Was this reply helpful? Yes No
LukeHendo 195 on at

Like (0)

Report

any other ideas?

Was this reply helpful? Yes No
BadrinathB 970 on at

Like (0)

Report

Hey Luke,

To narrow down the issue did you try to remove the Birthday field from Sync or you can try for one directional Sync.

docs.microsoft.com/.../control-field-synchronization-outlook

Was this reply helpful? Yes No
sanp 320 on at

Like (0)

Report

can you please mention outlook addin and onprem server version details?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
We have the same problem

CRM 8.2.3 OnPremise

Exchange 2016 CU10 OnPremise

Every time when the ServerSideSync Process sets the bearthday in crm the date is wrong. in the traces i have found a trace

Adding property crmxml to property map.
Mailbox '{2CD3769E-BFFC-E811-80B6-00155DD28B3D}',
Value: '<contact><address1_city>Nürnberg</address1_city><address1_country>Deutschland</address1_country>
<address1_line1>Pluto Straße 1</address1_line1><address1_postalcode>90471</address1_postalcode>
<lastname>Maier</lastname><firstname>Sandra</firstname>
<statuscode>1</statuscode><birthdate>1986-02-03T23:00:00</birthdate>
<telephone1>0911 123456789</telephone1>
<contactid>{13EC0489-C2FC-E811-80B6-00155DD28B3D}</contactid>
<ownerid>{2AD3769E-BFFC-E811-80B6-00155DD28B3D}</ownerid></contact>'.

the corect Date is 1986-02-04

All systems and settings in the same Time Zone (GTM+1).

Was this reply helpful? Yes No
Thomas Bergmair 35 on at

Like (0)

Report

same problem. all onpremise. any solution?

Was this reply helpful? Yes No