How to get results count from a workflow (without using GetSelectedFeatures activity)

Chris Dunlop

8. Juni 2017 15:55

Hello.  I'm building a workflow that uses features that have been returned, either from an Identify operation, or the Global search box.  I was using the GetSelectedFeatures activity to access these features.  One thing I noticed though, is that when you use GetSelectedFeatures, it immediately passes the entire results set (geometry and attributes) to the server.  If I do this on anything over ~2000 parcels, it either times out, or gives a 404 error message. 

 

Any ideas on how to get around this?  Even getting a feature count would be useful, so I could intercept too-large requests, but I don't know how to do this without invoking GetSelectedFeatures.  The old chicken-vs-egg dilemma...

 

Thanks!

 

Chris

0

• 

  Chris Dunlop

  8. Juni 2017 16:30

  Hi Nico.  Unfortunately that won't work.  The problem is, the GetSelectedFeatures activity immediately triggers a trip to the server.  If it's a large featureset, it has problems.  I need to be able to get the count *before* invoking the GetSelectedFeatures activity.

   

   

  0
• 

  Permanently deleted user

  18. August 2017 00:01

  Hi Chris,

   

  Unfortunately I don't think it will be possible to get the selected features from the results list and count them in your workflow without requiring a trip between the client and server.  You might want to look into Geocortex Workflow 5 (https://communities.geocortex.com/workflow)  though.  It runs on the client side only, so there are no trips between client and server.  It doesn't have a GetSelectedFeatures activity, but you can run the workflow from the results list's context menu and pass the selection in like an input argument.

   

  Hope that helps,

   

  -Amanda

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.