Skip to main content

Now Available: Maintenance versions of Geocortex Essentials, Geocortex Viewer for HTML5, and Geocortex Mobile App Framework

Comments

16 comments

  • Permanently deleted user
    Jordan,

     

    I get an error when I try to open the 'Geocortex Report Designer.zip' file.  Error states 'Windows cannot open the folder  The Compressed (zipped) folder 'Geocortex Report Designer.zip' is invalid.

     

    After looking at the last install file, it was an exe as opposed to a zip file.  I changed file extension to .exe and it ran just fine. 
    0
  • Sean McClurkan
    So I have a workflow experiencing the issue with "NaN" values in serializing objects.  I upgraded to Essentials 4.5.1 and HTML5 2.6.1, but the workflow is still erroring on "Unexpected token N in JSON at position 900".

     

    What do I need to do to ensure that the workflow is saved/operating at the latest version?  I opened the workflow, added an Alert, and then saved it.  Does the Essentials installation automatically upgrade the version of Workflow Designer?  Do I need to manually re-install Designer from the stand-alone executable on the Downloads page?
    0
  • Permanently deleted user
    Did anyone receive an email notification about this release? I stumbled across the new download today and had no idea it was ready!
    0
  • Permanently deleted user
    Hi Laura,  

     

    I can confirm that I received an email, but I'd be interested to know if anyone else had a problem with notifications.  Are you subscribed to the Announcements forum?

     

    Thanks! Pandora
    0
  • Permanently deleted user
    I am subscribed to the Announcements forum and I did not receive a notification.

     

    - Heather
    0
  • Permanently deleted user
    Ack!  Thank you for your reply, Heather.  We'll look into this to determine what is going on.
    0
  • Permanently deleted user
    I definitely haven't gotten the last few Announcement emails.

     

    After my upgrade to 2.6.1 I'm receiving an error when running my Geocoding workflows after the (same as when i tried to upgrade to 2.6). I get a "There was a workflow error running activity: Unexpected token N" message. I was told this would be fixed with the 2.6.1 HTML5 viewer release. Any help? Basically any workflow I have that tries to locate an address now throws an error message. 
    0
  • Permanently deleted user
    We are looking into the email notification issue now, and I hope to have resolution shortly.  

     

    I will also have someone look into the issues reported by Sean and Laura. 
    0
  • Permanently deleted user
    Hi Laura,

     

    Are you using Chrome version 50?  Can you try using Internet Explorer if you are?  This may be related to the Chrome update.

     

    Thanks,

     

    Wayne
    0
  • Stefan Schweigert

    Hi Laura,

    If possible, could you provide a workflow which is exhibiting this behaviour? You can send it to me at sschweigert@latitudegeo.com

    Thanks, Stefan

    0
  • Permanently deleted user
    Hi Stefan, I just emailed you my locate address workflow. Thank you! Wayne - I tried launching my workflow in IE instead and I got the same error message.
    0
  • Stefan Schweigert

    Hi Laura,

    Thanks for providing your workflow. I'm able to reproduce this issue and unfortunately, there is no workaround for this issue. I will raise this issue with developers for the next release.

    Thanks, Stefan

    0
  • Permanently deleted user
    Thank you for looking into this. I'm a little frustrated because I already reported this when the HTML5 2.6 viewer was released, and I was told to wait for 2.6.1 and the issue would be fixed then.
    0
  • Permanently deleted user
    Any idea when the next release 2.6.2 will be?
    0
  • Permanently deleted user
    Today I upgraded my test server to the latest release (for Essentials & HTML5), and I am still having this issue.

     

    All of my workflows that use a Geocoding activity throw errors similiar to: 

     

    There was a workflow error running activity: Unexpected token N in JSON at position 3619

     

    The issue is when it's trying to Convert the geocode resulting to an Address List, it does not like that I want to take the LOCATION part of the address and then convert it into a MapPoint. These workflows always worked up until these latest releases. 

     

    Does anyone have a fix or work around? We can't move forward until all of our tools work, and I was told to keep waiting for the next release, and then the next and the next. Still no help.
    0
  • Amanda Frech
    Hi Laura,

     

    I've just responded to your other post about this, but I'll do so here as well in case anyone else has the same issue.  We have two separate issues filed that are related to the "Unexpected token N" message in workflows. The specific use case of having DataItems used by the Display Form activity was not resolved with the fix for GE-7933 in Essentials 4.5.1.  This (GE-8630) will be resolved in Essentials 4.7.

     

    Hope that helps,

     

    Amanda
    0

Please sign in to leave a comment.