How to supply "RemoveFeatureFromResults" command with correct Geocortex Feature?

Permanently deleted user

11. Dezember 2017 19:09

I am stumped on how to supply the correct Feature to the "RemoveFeatureFromResults" external command (through the Run External Command activity).  Obviously, using this command in the Run External Command activity requires a Geocortex.Essentials.Client.Tasks.Feature as the command parameter.  I am unaware of how to supply this type of Feature to the activity.  Can I obtain this feature from some other activity (like the Get Selected Features activity)?  I certainly know how to work with Esri Features in a workflow, but finding how to get an Essentials Feature is a bit of mystery.

 

Can anyone clarify this for me?

 

Thanks!

0

• 

  Jostein Svegården

  12. Dezember 2017 09:10

  Michael, I recently had a support case where I asked Latitude the same question. The answer I got was:

   

  "You cannot use this command on an ESRI feature in a workflow, and this command can only be used in the viewer that is run from a button that is listed under the context menu for the feature results."

   

  My comment: This kind of information should be in the documentation

   

  Latitude then suggested to do this by making a new selection excluding the feature that you want to remove from results. I haven't implemented this all the way, but I dived a little bit into it. From the GetSelectedFeatures activity, you get a list of EssentialsFeatureSet - one featureset for each of the layers that you have results from in the results window. EssentialsFeatureSet has a property EsriFeatureSet that you can use to work with Esri Features as you are used to. I would then try to get a list of ObjectIDs from the EsriFeatureSet, and make a new selection excluding the ObjectID I want removed from the results list.

   

  If you manage to implement this, it would be nice if you could post it here :-)

   

  Jostein

  0
• 

  Permanently deleted user

  12. Dezember 2017 16:34

  Thanks Jostein for that info!

   

  I too would like to chime in about the documentation for Geocortex.  Although it is better than nothing, it leaves a lot to be desired.  I would hope that Latitude would put a bit more effort into making the documentation "richer" by including examples, when and where you can use the various commands, etc.  This would help tremendously and save a ton of time and support calls.  I hope in the future Latitude will take the time to improve this part of their product.

   

  I'll let you know what I come up with.  Thanks again,

   

  Michael

  0
• 

  Permanently deleted user

  12. Dezember 2017 19:22

  Thank you for your feedback relating to the documentation. We do appreciate it!

   

  I will pass it along to the documentation team for their consideration.

   

   

  0
• 

  Permanently deleted user

  12. Dezember 2017 23:15

  Thanks Pandora.

   

  While we are on the subject of how to improve Geocortex documentation, I am wondering if I can make a suggestion: Why not open your documentation up to editing in a wiki style to the registered users of your products.  The registered users are the ones who use the documentation the most and we are probably the ones who could help the most to improve it.

   

  Using that strategy, Latitude would just curate the wiki edits and approve them for submission into your documentation.  I think you would see a huge improvement in your docs in no time and the docs team would have less of a burden to try to figure out what users are looking for.

   

  Just an idea ;)...

  0

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