ArcGIS Feature Layers in Geocortex Essentials - Date Formats

Permanently deleted user

18. August 2014 14:03

The topic of date formats for feature layers has come up often in this Forum with no resolution/workaround as far as I can tell.

It appears the Identify functionality and the Edit Attribute functionality for a feature layer displayed in either a Silverlight or HTML5 Viewer display the same date value differently.

Configuring the feature layer to use the Geocortex Services Enhancement Proxy Server as suggested does not resolve the issue.

Below is some same data to illustrate the issue (GE 4.1, SL 2.2, ArcGIS 10.2.1) :

 

ArcMap

The source data (stored in Database local time)

/customer/servlet/servlet.FileDownload?file=00P6000000elth2EAA

 

Geocortex Essentials (Map Service, No Proxy)

Date value and format displayed correctly

/customer/servlet/servlet.FileDownload?file=00P6000000eluHKEAY

 

Geocortex Essentials (Feature Service, No Proxy)

Identify - Incorrect date/time value and format

10 hrs has been added to the time and the date format is now mm/dd/yyyy

/customer/servlet/servlet.FileDownload?file=00P6000000em1WWEAY

Edit Attributes  - Correct date/time value incorrect date format (now mm/dd/yyyy)

/customer/servlet/servlet.FileDownload?file=00P6000000elzqhEAA

 

Geocortex Essentials (Feature Service, Geocortex Services Enhancement Proxy – Resolve Coded Domains)

Identify – Correct date/time value, Incorrect date format (now mm/dd/yyyy)

/customer/servlet/servlet.FileDownload?file=00P6000000elth7EAA

Edit Attributes – Incorrect date/time value and format

10 hrs has been subtracted from the time and the date format is now mm/dd/yyyy

/customer/servlet/servlet.FileDownload?file=00P6000000eltg9EAA

Is anyone able to offer a solution/workaround to this issue?

Tim

 

 

 

0

• 

  Permanently deleted user

  19. August 2014 08:30

  Tim,

  this old chesnut!

  We basically don't let the user edit any dates in the SLV client. We did have a tool to edit the dates via a workflow that catered for our UTC offset etc... so it would write the 'local' time and present this in the identify results as you've found. Now we have a 'listner' on the ' Save edits' button that will update the date fields for us in a more efficient manner. We've had the latter written for us by a local mob here in Melbourne, but we had the workflow in place for a couple of years while the whole debate about storing local vs UTC seems to be still raging. LG expect us to store UTC dates, but for those across one time zone, including our friends across the ditch in NZ, this has not been received well. 

  One quirk we did find, is that the date will switch around to DD/MM/YYYY once the 12th day of the month came around. AAM were here looking at it also. I'm not sure it's in the 2.2 viewer, as this was in 1.9.1, so I need to do some testing on that again.... weird one! 

  love Hema maps by the way - any spare discs lying around  ; )

  GF

   

  0
• 

  Permanently deleted user

  10. Februar 2015 06:01

  I'm not sure if this is similar or not, but when I identify, query, or search via a workflow I come up with a different date and none are consistant.  Is this fixable?  Or do I have to just convert all my dates to a string?

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.