onClick action error: language-feature-sources-error

Permanently deleted user

March 02, 2021 23:45

I am getting an error when I click on some layers in my map in Geocortex web.

The popup has no custom configuration and works fine in Portal Map

Running Geocortex Web Version 5.11.0

Screenshot attached,

 

inspect tool text:

arcgis-extensions-core.min.js:1 [map]: An error occurred while executing the map's onClick action.

_log @ arcgis-extensions-core.min.js:1

arcgis-extensions-core.min.js:1 Error: language-feature-sources-error

  at r (main.907e3188.chunk.js:1)

  at t._addFeatures (/webviewer/static/js/common/components/FeatureDetails~web/components/feature-summary.5d9fe969.chunk.js:1)

  at async displayResults (/webviewer/static/js/common/components/FeatureDetails~web/components/feature-summary.5d9fe969.chunk.js:1)

  at async t._executeIfApplicable (/webviewer/static/js/common/components/FeatureDetails~web/components/feature-summary.5d9fe969.chunk.js:1)

  at async Promise.all (/webviewer/designer/index 0)

  at async Object.n [as parallelEach] (arcgis-extensions-core.min.js:1)

  at async o (main.907e3188.chunk.js:1)

  at async r.execute (main.907e3188.chunk.js:1)

  at async I._executeOnClick (/webviewer/static/js/web/components/Map.36dd358b.chunk.js:1)

  at async I._onMapClick (/webviewer/static/js/web/components/Map.36dd358b.chunk.js:1)

0

• 

  Tania Taylor

  June 15, 2026 15:18

  When I check the network. "The search component is throwing a TypeError when destructuring featureResult inside the query results handler, causing the parent QueryError map to fail." Is this common

  0
• 

  Malcolm Walker

  • Community-Manager

  June 15, 2026 16:15

  Hi Tania,

  I believe this is a known issue, but a bit obscure. From our bug tracker:

  • this issue is triggered by layers that have an extent listed on their REST endpoint with coordinates that exceed the bounds of the layer's spatial reference.  Eg. for a Web Mercator layer, if any of the layer's extent's x/y min/max values exceed ~20,000,000
  • this issue only happens if there aren't too many results near the current map extent when the search is run.  It happens when the search extent is expanded several times.

  So, the workaround is to re-publish your layer and ensure that the layer extents fall within the bounds of your target spatial reference.

  I do not anticipate we will publish a fix for this bug, since it is a result of Esri's service publishing something that is unusual - we would not expect a layer's extent to exceed a spatial references' extent.

  0
• 

  Tania Taylor

  June 16, 2026 14:43

  Thank you, Malcolm, for your response.

  I spent the rest of yesterday reviewing my services and feature classes, and they all fall within the ~20,000,000 Web Mercator limits you mentioned. Because of this, republishing the services would not resolve the issue.

  The problem seems isolated entirely to our Utility Network (UN) services, but importantly, these exact same layers work perfectly fine in our legacy GeoCortex environment. The failure only occurs in VertiGIS Studio. Furthermore, we noticed that your own public VertiGIS demo site throws this exact same red banner during use.

  To isolate the cause within VertiGIS, I tested several service types across our workflows:

  • UN editing services (Throws error)
  • UN services with definition queries at publication (Throws error)
  • UN MIL and feature services with no definition queries (Throws error)
  • UN File Geodatabase (FGDB) services (Works fine / No error)

  Only the UN FGDB services bypassed the red banner. Additionally, to rule out other variables, I tested non-UN services that utilize branch versioning, M/Z awareness, and archiving. None of those services experienced the issue.

  Since these services behave correctly in GeoCortex and their extents are mathematically valid, this looks like a regression or handling issue in VertiGIS Studio. Could you verify if your public sample site utilizes the Enterprise Utility Network, branch versioning, or M/Z aware layers? Knowing how the sample site is published might help us pinpoint exactly why the VertiGIS search widget handles these valid REST endpoints incorrectly when expanding the search extent.

  0

Please sign in to leave a comment.