Geocortex Analytics fails to read the correct dates;

Permanently deleted user

May 24, 2017 09:15

Hi All,

 

Despite the fact that Today is 24/5, the Geocortex Analytics read 3 days after the current date (25/5, 26/5, 27/5) which are not coming yet!

 

 

 

 

What might be the issue here?

 

Best,

 

Lubna

0

• 

  Permanently deleted user

  May 24, 2017 20:29

  Hi Lubna,

   

  The time that is shown in the reports comes from the client relay.  If your users are in a different time zone, or have their clocks set differently on their PCs, the time that is reported in Analytics will reflect the time on their PCs.

   

  I hope this helps!

   

  Thanks,

   

  ?Danny

  0
• 

  Permanently deleted user

  May 25, 2017 20:02

  Optimizer respects the server time and thus never records time in the future!

   

  _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000Grnk&feoid=Body&refid=0EM60000000Uju8" _/_img_

  0
• 

  Permanently deleted user

  May 29, 2017 10:30

  Hi Danny,

   

  What is the idea of reading the time of the end user machine in case there is a possibility that this time is wrong!

   

  Best,

   

  Lubna

  0
• 

  Permanently deleted user

  May 29, 2017 15:43

  Hi guys,

   

  This questions overlaps with a question you asked in another thread.  See my reply below:

   

   

  Hi guys,

   

  I had a chat with the product manager about this, and I think I've misspoken here.  I apologize for the confusion, let me try and clarify:

   

  The time is collected from the user's browser and converted to UTC.  It is then sent to Analytics.  Analytics displays the time in reports in the report viewer's local time (converted back from UTC).  

   

  That being said, you should not be seeing times that are hours or days ahead.  Can you please open a support case at your convenience, so we can collect your logs and data for analysis?

   

  Thanks!

   

  Danny

   

  ---

   

  If the time on the user's machine is wrong, then it will cause an offset in Analytics.  

   

  Thanks,

   

  Danny

  0

Please sign in to leave a comment.