Layer Catalog layers not being added to Layer List

Andrew Ritchie

December 23, 2020 02:02

Hi there,

 

Users have just reported this to me, so I'm assuming it's a new issue since I federated ArcGIS Portal with Server and swapped from anonymous use to Portal security.

 

 

Geocortex Essentials 4.13.3, HTML5 Viewer 4.13.3

 

 

When trying to add layers from the Layer Catalog to the Layer List, some layers simply don't get added to the Layer List. Using Chrome Developer tools, I can see the error: "We can't add the same service layer twice to the layer list"

 

 

So the issue appears to be that I have some layers from a service connection added as part of the map, but I'm then trying to add additional layers from the same service connection via the Layer Catalog - is this intended behaviour that I simply haven't noticed before?

 

 

Editing the map and adding one of these layers through 'Add Map Service' works fine, so I don't know why the Layer list is complaining about having the same service layer twice, but I can do this through the map editor.

 

 

Any thoughts?

 

 

Cheers,

 

Andrew

0

• 

  Permanently deleted user

  February 23, 2021 22:35

  Hi Andrew,

   

   

  Did you happen to get to the bottom of this issue? We recently federated our ArcGIS Server as well and started seeing this error for certain layers in our site as well!

   

   

  Cheers,

   

  Nate

  0
• 

  Andrew Ritchie

  February 23, 2021 23:09

  Sorry for not coming back to the thread! I got a response from our Geocortex supplier: "With a layer catalog, you cannot reference layers from the same map service that is already present in the base site. This is standard behaviour for Geocortex Essentials and is mentioned in the the documentation here: https://docs.geocortex.com/essentials/gvh/latest/admin-help/Default.htm#gvh/admin/modules/layercatalog-module.htm The behaviour shouldn't have anything to do with your recent upgrade to 10.8 so you probably just haven't noticed that behaviour previously." The documentation checks out - but good to hear that I'm not imagining this change in behaviour. I haven't fixed it yet - but one idea I had was to stop relying on service mxds, and just add our Geodatabase as a DataStore - shared with Portal - that way all feature classes get an individual service.

  0
• 

  Permanently deleted user

  February 24, 2021 00:41

  Thanks for the info ... I appreciate it!

  0

Please sign in to leave a comment.