Report not reflecting Event Time Zone

Hello, 

I am running into an issue with all of my reports, and I don't believe I had this issue in the past. 

When I run any filtered report on meetings, the report result will automatically adjust all of the events to my timezone, regardless of where the meetings occoured. This gives me results like lunch meetings at 5 PM, etc and a lot of other data that simply doesn't make sense. 

I need to be able to run reports based on the data that was entered into the system, without that data being changed or manipulated.

If I am in Eastern Zone, and I run a report for someone in the Pacific Zone, and he lists a lunch as 11 AM PST, I need my report to show 11 AM, not show as 2 PM, which is what it is currently doing. You can see how this can be difficult?

Is it possible to do this, or is there a specific type of report that I can run that will NOT auto-adjust to my timezone? 

Thanks

Parents
  • Hi  ,

    Sugar stores all date/time values in the database as UTC time. It does not store an associated time zone with those records, and the behavior you are seeing is expected in that all date/time values are presented based on the current user's time zone setting. The only way you could extract information without it adjusting for your time zone is to write SQL queries via Sugar's Advanced Reports module. With SQL queries, you could apply the offset you want to the applicable date/time UTC values. Be cautious with this approach as you need to account for records on either side of daylight savings time and apply the offset accordingly (e.g. -7 or -8 hrs for Pacific time depending on the time of year the meeting was scheduled).

    Chris

Reply
  • Hi  ,

    Sugar stores all date/time values in the database as UTC time. It does not store an associated time zone with those records, and the behavior you are seeing is expected in that all date/time values are presented based on the current user's time zone setting. The only way you could extract information without it adjusting for your time zone is to write SQL queries via Sugar's Advanced Reports module. With SQL queries, you could apply the offset you want to the applicable date/time UTC values. Be cautious with this approach as you need to account for records on either side of daylight savings time and apply the offset accordingly (e.g. -7 or -8 hrs for Pacific time depending on the time of year the meeting was scheduled).

    Chris

Children