ResultsTable Features with assigned geometries do not behave like regular Features

Sean McClurkan

9. November 2017 13:32

I have a workflow that executes a SQL Query activity resulting in a DataTable. I convert the DataTable to a Featureset and then assign geometries to all the features. I then do a Select Features against a configured layer in my application.  Then I ShowResultsTable for the named collection from my Select Features activity.  But the ResultsTable created this way does not automatically show the highlighted features in the collection in the map, or center and zoom on a selected feature in the ResultsTable, or show the Feature Details for a selected feature in the table.

 

If I execute a QueryTask activity against a configured layer in my applicaiton and then do a Select Features activity, those features will center and zoom and show their details when clicked.

 

What do I need to do differently to get my features with assigned geometries to behave exactly those that already come with geometries?

0

• 

  Permanently deleted user

  4. Januar 2018 23:09

  Hi Sean, 

   

  In a case like that, I would start by logging or alerting the json from your featureset, eg. featureSet1.ToJson().  Then log or alert the json from a known working test (you mentioned "If I execute a QueryTask activity against a configured layer in my applicaiton and then do a Select Features activity, those features will center and zoom and show their details when clicked").  Compare the two featuresets and see if there is anything obviously different, like a missing spatial reference property.

  0
• 

  Tom Lenarcic

  21. Mai 2020 18:57

  Hello Sean:

   

   

  Did you ever get this resolved?

  0
• 

  Sean McClurkan

  21. Mai 2020 19:02

  I'm not sure. I've slept since then. I think i wound up creating actual features in a featureclass to use instead of trying to create them dynamically at runtime.

  0
• 

  Permanently deleted user

  22. Mai 2020 21:53

  I was just troubleshooting a coworker's workflow where features were not highlighting and the pushpin would not show up on hover for features from the SelectFeatures activity. In our case it was because when we queried the features, he was passing an "Out Spatial Reference" to the Query Task activity that wasn't set. Once I set it to a valid Spatial Reference, our highlights and pushpins showed up.

   

   

  Not sure if that applies to you as you're building your own feature set, but it may be worth checking how you're creating your geometries and seeing if they have a spatial reference defined.

  0

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