An unknown error has occurred - Query or Filter
GE 4.10 and GVH 2.11 - after upgrade
Both the Query and Filter tools randomly thow an error when selecting a layer from the list. "randomly" as in, not always the first time a layer is selected, sometimes after the 2nd or 3rd layer selected, even before a query or filter is executed. Once the error has occurred, it re-occurs with every subsequent selection and the field list doesn't update. Dev Tools Console reports the following:
_img_ alt="Dev Tools snippet" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=906f2000000kA3H&feoid=Body&refid=0EMf2000000g0Fj"_/_img_
0
-
Hi Scott, 0 -
I am also having the same issue after upgrading. In my case it happens everytime I change the layer in the Query window. 0 -
Thanks Wayne, 0 -
Hi Scott, 0 -
Wayne, 0 -
I've seemed to notice it when you have a mix of secure and non-secure map services. Either way, we are getting alot of complaints from the users.. 0 -
Hi Bill, 0 -
What is the bug number of this issue? 0 -
Hi Nico, 0 -
Is this fixed in the maintenance release? 0 -
Yes, it is. You should not see this issue in GVH 2.11.1 0 -
We have installed the recent upgrade (Geocortex Essentials 4.10.1 and Geocortex Viewer for HTML5 2.11.1). The Query issue is fixed but we are still not able to save queries in the viewer or see Administrator Defined queries. Is anyone experiencing this issue? 0 -
hi @Bobby, yes we are having the same issue. 0 -
Hi, 0 -
We're experiencing the same issues as what @Bobby describe. I contacted support and they mentioned it is a known issue (BUG 24287) that is being tracked. They didn't mention when it is supposed to be fixed. I just upgraded the viewer to 2.11.2 on our test environment, and the bug still persists. 0 -
For the record, BUG 21152 was fixed in 2.11 and a new bug was introduced (BUG 24287) and it is fixed for 2.12. Version 2,12 is due to be released around January of 2019.
Wayne
0 -
We're experiencing the same "An unknown error has occurred" in Query builder with 2.12. 0 -
The error seems to occur in combination with a "Could not retrieve suggestion for [attribute name]" for large datasets. 0
Please sign in to leave a comment.
Comments
18 comments