Supports Dynamic Layers of Null

Permanently deleted user

May 29, 2015 00:07

Just upgraded my local machine to the new Essentials v4.3 and the GVH v2.4. Ran one of my existing workflows on the upgraded site

and received an error "Cannot read property 'SupportsDynamicLayers of null'

Opened the existing workflow with the new Essentials Workflow Designer v4.3.0.1271

Walter

 

0

• 

  Permanently deleted user

  May 29, 2015 00:27

  In the lastest WorkFlow Designer help file, it states that for the "GetMapServiceInfo" activity, that the layer source should only be populated for "dynamic" layers.

  I've had this set before and the workflow ran fine. The layer that I'm working with is not dynamic.

  Is this what's causing the error?

  Walter

  0
• 

  Permanently deleted user

  June 18, 2015 04:30

  Walter,

  Did you find an answer to your question about the "Supports Dynamic Layers of Null" error message.  We are having the same issue in our migration to 2.4.

  Thanks,

  Dan

   

  0
• 

  Permanently deleted user

  June 18, 2015 05:57

  Hi Dan,

  "Cannot read property 'SupportsDynamicLayers of null' is usually related to an incorrect Query Service URL.  "SupportsDynamicLayers" is the first thing the activity does with the URL and if the check fails, due to an incorrect URL, that is the first error that is thrown.  I would verify the URL, by placing it in a browser, to make sure it is valid.

  Regards,

  Wayne Richard   Latitude Geographics Group Ltd. Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7 Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com Developers of Geocortex web-based mapping software | www.geocortex.com An Esri Platinum Business Partner

   

  0
• 

  Permanently deleted user

  June 18, 2015 06:37

  Thanks Wayne!

  I appreciate your response and I will verify my query service urls.

  Thanks for monitoring the forums.   

  Dan

   

   

  0
• 

  Permanently deleted user

  May 02, 2018 15:47

  I also got this error message when I imported a workflow from another site but failed to realize that the map ID for one of my layers was incorrect in the owrkflow input arguments.  This post helped steer me in the right direction!

  0

Please sign in to leave a comment.