Hoppa till huvudinnehållet

Global Search For Specific Map Services

Kommentarer

6 kommentarer

  • Permanently deleted user
    The problem seems to be that my global search in my work flow is only taking the first group in the results list. Please see attached.

     

    But I need the results from the second group in the list. Is there any way of being able to select any one of groups after the global search is run?

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=907f2000000fySM&feoid=Body&refid=0EMf2000000kAVQ" _/_img_

     

    Walter

     

     
    0
  • Permanently deleted user
    Use "Set Layer Definition" and supply the service ID value to ensure that the search results show this to the top of the results pane.

     

    Walter
    0
  • Permanently deleted user
    The "Set Layer Definition" seemed to work, but if I run my work flow consecutively, the work flow's global search does not always place the search results at the top of the search results.

     

    How can one ensure that search results for a specific map service always be placed on top of the search results pane?

     

    Walter
    0
  • Dan Giersz
    Why don't you use a QueryTask on the map service instead of the Global Search?
    0
  • Permanently deleted user
    Dan,

     

    At the time when the client runs the workflow, they are unaware of the particular names of certain locations. Therefore, the global search in the workflow is best suited for this, but require that the search results for a particular map service be placed on top of the results pane.

     

    Walter
    0
  • Permanently deleted user
    Hi Walter, 

     

    The global search command only accepts one command parameter, the text string that you need to search on.  If you are using version 2.8+ of the viewer, I think the easiest answer would be to train users to select the desired layers from the grouped results list, or make it easier for them to distinguish those in the results list.  Another answer would be to use QueryTask activities for all of the layers that they might be interested in (if it's not an unreasonable amount) instead of GlobalSearch

     

    You should be able to get back the results from a global search by putting an external delay in the workflow and then using the GetSelectedFeatures activity.  From there you could likely manage the results and reselect them in the desired order.  However I don't recommend this process because there isn't a good way to tell how long that delay should be.  Global search could take 0.1 or 15 seconds to finish, depending on how many services and fields it needs to query, and how fast your services are.  Having to reselct the features isn't great either because it adds a lot of time to the workflow.

     

    Hope that helps,

     

    Amanda
    0

Du måste logga in om du vill lämna en kommentar.