Oh Async: Introducing the Chef "Mr. Processor"
Update Rollup 3 for Microsoft Dynamics CRM Server 2011

Fun with Dates

In this incredible world of both technology offering calculated date and people capturing data from all over the world the two concepts can sometimes collide!

Take for instance the world of dates.

Microsoft Dynamics CRM offers UTC adjustments, personal settings and Date and Time fields. What this means is that depending on how you have your computer configured and your Dynamics CRM Personal Options the dates that you enter are adjusted.

Microsoft Outlook does this as well. If  I was to setup a meeting with an associate in California for instance on my calendar for today the meeting would display as Eastern Time (2pm for instance), but for my associate (CRM Guru Marc Wolenik)  the date and time would display as (11am) and if we then added in another person such as a cool CRM Guru in Australia (Leon Tribe) the time would not only be different, the DAY would be different.   

So what happens when you start capturing these types of dates inside of Dynamics CRM for analysis or reporting?

If all the dates are entered by "humans" correctly configured for their local time zones then the software correctly handles all the adjustments. The only trick with regards to this set of considerations is that DATE Only fields are well not really date only so watch that!

If all the dates however are entered by other "Systems" then a bit more thought needs to go into the architecture. Take for instance a system that resides on a server in a data center that is capturing date information based on that servers date. If you then take that date and enter it via an integration, how would you expect Dynamics CRM to react?

How would that date be managed?

Do you want it to be fixed? or adjusted?

If you want it to be adjusted, how are you going to tell the system to adjust it?

What if you want it to be a date field BUT you want to lock it to a certain time zone?

These are the joys of the world of global!