You’re offline. This is a read only version of the page.
2,585
Hello Folks,
I have this weird issue.
CRM version : 8.1.0.359 It is an On-Premise version
some of the contacts in CRM have been updating recently. A quick look in the Audit history revelaed the Birthdate field is getting updated.
example :
before 22/10/1988 12:00am
after 22/10/1988 1:00 pm
I have tried disabling the plugins on contact, checked the server sync, checked the integrations but all in vain. I am still unable to find what's causing the birthdate to change.
1) would changing the birthdate from "user local" to "date only" help? (CRM is in NZ timezone)
2)are there any other ways to check what's causing the birthdate to jump?
Thanks!!!!
*This post is locked for comments
Not sure but could be related to timezone difference between user's outlook/mailbox and user's CRM timezone.
Worth raising it with Microsoft to get the confirmation. Also, do share response from Microsoft here and mark you response as verified to help other facing the same issue :)
Hello guys,
Finally, figured the source of the problem.
Setting the mailbox sync for "Appointments, contacts and tasks" to NONE has stopped the update on birthdate field.
Very weird.
Any clue about this?
Thinking to raise an MS Support request as office 365 settings are fine.
Thanks All!!! :)
Hi Again!
What is your Birthday date entry, is it Manual? or with some input method?
tip, just to confirm if it from serverside or manual updates, just remove the field from form so that any JS or BR will not work on it. then you can further dive down based on audit logs
Hi Sreekanth P,
A couple questions to ask yourself.
I hope this helps you to narrow down the cause of the issue.
Hello @Sreevalli Balleda
The birthdate getting updated is shown in Audit history. I cant seem to find any process which is updating the birthdate. I have checked the plugins/workflows and disabled them as well.
is there any other way which we can find whats causing this update?
Hi,
If you are seeing date change only on form but not in audit that means users time zone changed and it will reflect on form. but when you seeing changes in DB level or audit then there is a background thread running to update the date.
If you see the the time getting added by 13hrs every time then you check the timezone changes and the triggers for the same.
Microsoft recommendation for Birthday fields behaviour is DateOnly. https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/behavior-format-date-time-field but as you want to change now, check the values before. if all of your old values are 12AM and now its 1PM then its obsolutly works,but if there is a case like old vlaue is 1PM and updated value is 2AM next day then you will end up with issues.
Hi,
You need to first find the reason of why this has happened and if this is happing on a consistence basis? If yes, what is the trend of the update. With respect to timezone, for BirthDate, it makes more sense to have it as date only irrespective of the issue. Check the date of the update and see if these are on the same time duration, if yes then this could be related to some bulk update happened.
You need to find if this is still happening or not, if yes then when exactly this happens.
Hope this helps.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (