Skip to main content

Date fields filled with today without any reason

Permanently deleted user

We use Geocortex Essentials 4.2 and HTML5viewer template 2.3

 

We have a viewer with a feature service which has a layer with a few date fields.

 

If we select an object for which the date fiels are not filled (so they're N/A), and then, if we click on the button Edit Object, then suddenly the date fields are filled with the date and time of the moment.

 

This problem arises when we use the HTML5viewer on a desktop.

 

Obviously, we want empty dates to stay empty, until the user wants to change that.

Has anyone got the same problem?

 

Has anyone got a solution to this problem?

 

 
0

Comments

4 comments

Date Votes
  • David Major

    Yes we have this problem. The "solution" was to fill in all the dates as something arbitrary and obviously not real. But I would much rather have it remain blank.

    David

    0
  • David Major

    Just wanted to mention that the workaround to pre-fill in the dates does not work! It does not stop the date field from being filled in with the current date when editing a feature.

    David

    0
  • Permanently deleted user

    We are facing a similar issue with the GE 4.2.2 and HTML5 2.3 (this was never an issue with GE 4.1.5 and HTML5 2.2 ). 

    We have been using the GE 4.1.5/HTML5 2.2 configuration since last April on Apple iPad's collecting sign and pole inventory for our Transportation Operations group.  Everything was working very well until Apple released the newest iOS 8.x, at which point we lost the ability to interact with the 'I Want To' menu. 

    We now have an external test server running the latest GE 4.2.2 and HTML5 2.3, in the hope that the newest version would solve the 'I Want To' issue.  The good news, it has solved that problem.  The bad news, install and expirory dates are now been self-populated (where they were not in the previous GE 4.1.5/HTML5 2.2 releases).  This is a huge issue as we rely on these fields for display purposes.  A new asset could be added to the map and then automatically disappear from the map (we have a Query Definition set on the asset to look for NULL values for expiration for display purposes) as a erroneous retire date has been self generated which is extremely annoying!!!

    Seems like we're taking two steps forward and one giant leap back.  Can Geocortex support please advise on this issue?

    0
  • Permanently deleted user
    Hi all,   This is a known issue in GVH 2.3 and it will be fixed in the upcoming 2.4 release. In the new release, if the default for a date in the template is null, then the datepicker will show it as null when creating a new feature.   Hope it helps,   -Alejandro
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post