Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
ActualCloseDate discrepancy between UI and data entity RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have an on-premise installation of Dynamics 2011 and have noticed something which we can't explain in the data stored by Dynamics. We have a "view" showing 'opportunities' which have been closed in the current month, and these records are listed in the Dynamics UI just fine, both in the View list and when opening up to look at the details. I've been exploring the data stored in the Dynamics database tables and have noticed that often the date/time shown in the web UI for the "Actual Close Date" field is farther in the future than the ActualCloseDate date stored against the Opportunity entity.

    So for example some of our records have an ActualCloseDate against the entity of 31-May-2015 23:00, but show up in the UI as having been closed on 1st June. Likewise some records are stored as 01-Jun-2015 23:00 but show up in the UI as 2nd June.

    Does anyone know why this might be? Is there additional logic performed by the Dynamics application which shifts the closed date forward in the UI compared to what's stored in the back end?

    Thursday, June 4, 2015 8:36 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Crm stores all datetime values in UTC time in the database. When a Crm user accesses the data via Crm it will display it in the timezone of that user. Similarly, when a user enters a datetime value, Crm will take that in the user's timezone, and convert it to UTC to store it.

    In the example you've given, the user is probably in British Summer Time, which is one hour ahead of UTC.

    Note that, if you access the data via the filtered views in SQL, the filtered view will do the conversion to the user's timezone 

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Thursday, June 4, 2015 8:46 PM
    Moderator