Using SetIdentifyCombineMode in a workflow with TabularResultsView

Permanently deleted user

March 28, 2018 22:38

I have a workflow that selects property sales in a feature set that is displayed in the TabularResultsView.  I want to use the SetIdentifyCombineMode (union) to allow the user to click on unselected items and add them to the feature set.   After invoking SetIdentifyCombineMode and then clicking on a feature (with the identify tool) the result is displayed in the Results List (Left side of the screen) in what appears to be a new feature set.  I want the clicked item added to my existing results in the tabular view.   How do I control where feature sets/results are being displayed after using the SetIdentifyCombineMode (union)?  This is a toggle tool that is in the FindDataControlRegion and seems to have this same strange behavior as an out of the box tool.  I assume the answer is somehow managing the featuresetcollection names when using the identify tool.  Thanks for any help you can provide.

0

• 

  Permanently deleted user

  July 20, 2018 18:41

  HI Dan, 

   

  I don't think that you'll be able to reliably combine results from an identify with existing results from a workflow into one featureset collection.  At least not with the out of the box tools. Identify uses a new collection id every time you use the tool without "Add Results" enabled.  Your first Identify in a viewer session is "Identify0", then "Identify1", and so on.  If you reload a viewer fresh, do an identify, then use a workflow where SelectFeatures is set to use Collection Name "Identify0", then you can combine the results in one collection.  But that's not very useful in practice, since it won't work when the user changes the order or does any additional Identify operations.

   

  I'd recommend posting an Idea to request a configuration setting that lets the results collection manager automatically combine results from certain sources like workflow and identify when the combine mode is set to union.

   

  Or if you know which layers the users would likely be identifying features from, you could extend the workflow to let them select some geometry, and then have the workflow query those layers and handle the selection.

  0

Please sign in to leave a comment.