headercontroller search results options

[RhettZufelt]

Again, from the documentation:

<result>The container used to configure the search result's pop-up, [added at 3.5.] It has the following child tags:

<title>

Text title displayed in the resulting pop-up.

<description>

Text description displayed in the resulting popup.

You can configure the <title> and <description> using custom description functionality that allows you to display pop-up content using a custom sentence or paragrah structure and supports field substitution using a {FIELD} style syntax.

This seems like a nice option, however, it appears as if it is a child of the <geocoder> tag.  Seems like it should be a child of the <mapservice> tag, especially since it allows the description type custom popup info.

Doesn't make sense to me to have this under the <geocoder> tag unless ALL your locator/mapservices have the same attributes, etc.

The example in the documentation ArcGIS Viewer for Flex‌ is for a live traffic feed.  However, if I try to use something similar, but also want to use mapservices, OR, just mapservices but more than one, it will show a popup "template" but will not populate it unless they all have the same attribute names.

So, if I search my sewer manholes and have it set as such:

   <result>
      <title>Search result for {FacilityID}:</title>
      <description>
         <![CDATA[Popup for {FacilityID}
           <img src="{URL}" width="130" height="100" 
            hspace="0" vspace="0"/>]]>
      </description>
   </result>

Then search for a sewer manhole, I get:

If I then enter a street name in the same search box, I get:

Since there is not a FacilityID field in the streets layer the variables aren't substituted.

Am I just using this wrong, or is it pretty much only useable with only one geocoder and/or all searched services have the same schema (or at least fields)?

Thanks,

R_

[RobertScheitlin__GISP · Accepted solution]

Rhett,

  I have done some testing and I can see exactly what you are saying. I even tried to have some very generic result configuration like:

<result>
    <title>Search result for {Post_Stat}{P_Hyper}{Road_Name}{Local_ID}{Bin}:</title>
    <description>
        <![CDATA[Some data for {Local_ID}{Bin}{Post_Stat}{P_Hyper}{Road_Name}]]>
    </description>
</result>

The only thing I can say is to put in an enhancement request, but as 3.7 or 3.8 is probably the last versions to come out and they are mainly focused on bug fixes, it is pretty unlikely to happen.

Robert