locked
Differences in Time stamp RRS feed

  • Question

  • One of our MSCRM4.0 Application user complains about the difference in the time stamp when they created reports.They said that the times they created the records are displaying different in their reports.And also there are couple of other mismach in the time zones.

    I just gues that they made settings in their timezones,Probably by which this changes occur.But to my surprise when i saw the created date of these reports most of the reports just show me two timings : 23:00 and 7:00.Not sure what the way CRM Stores the timestamp data.

    And also even though if CRM Stores the data in different format or in some common standard timezone the Application layer may make use of the timezone settings to display the data properly.

    Thanks,

    Arif
    Mohammed Arif
    Wednesday, April 8, 2009 12:58 AM

Answers

  • Mohammed - you're exactly right - CRM stores date/time values at the server using "GST" or universal time. - which is essentially  a standard time from which everyone's timezone is measured - (I live in the US Eastern Timezone (gmt -5), which means the time on my watch is set 5 hours behind the 'standard' GMT time.)

    CRM translates the time records are created/edited to GMT when it stores that time - and if your user settings have the correct timezone marked, it will translate the GMT time to your local time when it displays that time.

    Problems usually are the result of 2 things that I can think of -
    1) a user not having their correct timezone set in their UI - (This is a per-user setting.)
    2) a report displaying a date/time field from the base tables or the 'non-filtered' views.  (The 'filtered' views in SQL will display the time adjusted to the user's timezone, based on their settings.)

    Check the user settings and ensure that everyone's account has their timezone set to the correct time. - (in CRM 'Tools' menu, select 'Options' and the user's current timezone setting will be on the first tab.

    One thing to be aware of, if the user has their timezone set incorrectly and it's changed, any appointments/task due dates etc that were setup under the old (incorrect) timezone may need to be adjusted to reflect the correct timezone. -
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Wednesday, April 8, 2009 2:17 AM
    Moderator
  • Exactly right. Now, make sure that people have their timezone set in both places: i.e. the CRM Options menu and the Windows Time.

    Regarding the 23:00 or 7:00 time stamp:

    This is because your date fields are "Date Only". If you don't include the time, CRM will save the field with time 00:00. Now, it looks like you have people working in PST and GMT (with Daylight Saving On) or CST and CET (without DST), so in the database you are going to see times as 7:00 (that's GMT when it's midnight in CST or PDT) or 23:00 (that's GMT when it's midnight in CET).
    Wednesday, April 8, 2009 2:47 AM
  • Mohammed - I think Alberto is correct in that your 'date-only' fields are showing the consistent timestamp. -

    Check to ensure that your reports are pulling from the 'filtered' views and not the regular views to make sure the information in the report shows the correctly adjusted date/time based on the user's settings.
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Wednesday, April 8, 2009 2:58 AM
    Moderator

All replies

  • Mohammed - you're exactly right - CRM stores date/time values at the server using "GST" or universal time. - which is essentially  a standard time from which everyone's timezone is measured - (I live in the US Eastern Timezone (gmt -5), which means the time on my watch is set 5 hours behind the 'standard' GMT time.)

    CRM translates the time records are created/edited to GMT when it stores that time - and if your user settings have the correct timezone marked, it will translate the GMT time to your local time when it displays that time.

    Problems usually are the result of 2 things that I can think of -
    1) a user not having their correct timezone set in their UI - (This is a per-user setting.)
    2) a report displaying a date/time field from the base tables or the 'non-filtered' views.  (The 'filtered' views in SQL will display the time adjusted to the user's timezone, based on their settings.)

    Check the user settings and ensure that everyone's account has their timezone set to the correct time. - (in CRM 'Tools' menu, select 'Options' and the user's current timezone setting will be on the first tab.

    One thing to be aware of, if the user has their timezone set incorrectly and it's changed, any appointments/task due dates etc that were setup under the old (incorrect) timezone may need to be adjusted to reflect the correct timezone. -
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Wednesday, April 8, 2009 2:17 AM
    Moderator
  • Exactly right. Now, make sure that people have their timezone set in both places: i.e. the CRM Options menu and the Windows Time.

    Regarding the 23:00 or 7:00 time stamp:

    This is because your date fields are "Date Only". If you don't include the time, CRM will save the field with time 00:00. Now, it looks like you have people working in PST and GMT (with Daylight Saving On) or CST and CET (without DST), so in the database you are going to see times as 7:00 (that's GMT when it's midnight in CST or PDT) or 23:00 (that's GMT when it's midnight in CET).
    Wednesday, April 8, 2009 2:47 AM
  • Mohammed - I think Alberto is correct in that your 'date-only' fields are showing the consistent timestamp. -

    Check to ensure that your reports are pulling from the 'filtered' views and not the regular views to make sure the information in the report shows the correctly adjusted date/time based on the user's settings.
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Wednesday, April 8, 2009 2:58 AM
    Moderator