Query Builder Error after GE4.10 and GHV5 2.11 upgrade

Permanently deleted user

July 30, 2018 04:01

Hi, we recently upgrade to GE4.10 and GHV2.11 and noticed the Query Builder tool on the toolbar not working.

 

 

 

Basically, when launch the query builder tool. It can pick up the fields of the first layer in the Data Source list, and the query builder works fine. But when I change the data source to other layers in the list, it failed to refresh the fields and throw out error saying “Could not find selected field from given fields.” Tried on both Chrome and Firefox same error. Has anyone noticed this?

 

 

0

• 

  Stefan Schweigert

  July 30, 2018 15:33

  Hello Jack,

  This issue will be fixed in GVH 2.11.1, which will be available in late August.

   

  The issue is caused by having field permissions configured for that particular user. Removing this setting, if possible, will allow you to query on this layer.

  Thanks, Stefan

   

  0
• 

  Permanently deleted user

  July 31, 2018 00:06

  Thanks Stefan.

  0
• 

  Permanently deleted user

  August 09, 2018 01:50

  It also occurs when field permissions are set using the anonymous user.

  0
• 

  Permanently deleted user

  August 09, 2018 01:56

  And also when the specific layer has no field permissions set, though we have to many field permission to remove them from all layers if that is what you meant.

  0
• 

  Permanently deleted user

  August 14, 2018 20:32

  Hi All,

   

  I am trying to use the query/filter tool for layers from the layer catalog. Ive tried granting field permissions but still no luck.

   

  Do these tools just not work until the next update?

  0
• 

  Stefan Schweigert

  August 14, 2018 20:58

  Hi Adam,

  Until 2.11.1 is released, which is currently planned for before the end of August, setting field permissions will cause errors to occur.

   

  Thanks, Stefan

  0
• 

  Permanently deleted user

  August 15, 2018 12:38

  Hi Stefan, 

   

  Thank you for the update. So is there any solution to get it to work before 2.11.1?

   

  Thanks

   

   

  0
• 

  Permanently deleted user

  August 15, 2018 15:11

  Hi Adam,

   

  Please submit a support case to support@latitudegeo.com and we will see what we can do.

   

  Thanks,

   

  Wayne

  0
• 

  Permanently deleted user

  January 06, 2019 17:23

  I have tested this on a fresh install of 4.10.3 & 2.11.2 and can confirm this is no longer an error.

  0

Please sign in to leave a comment.