Enhanced-Search-Widget-for-FlexViewer Part II

[RobertScheitlin__GISP]

All,

   I am pleased to announce the next release of my eSearch Widget.

http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

Version 2.5.1.7 - 4/19/2012
* Added ability to search (flat/standalone/no geometry) tables.
* This time all Zooming uses the same scaling (popup, datagrid, widget results, zoom to all).
* Added Relates icon/button to datagrids so that you can click on it in the datagrid to
  open relates choice dialog.
* Move all skins to a skins package for cleaner organization.
* Links that are not associated with a field now work.
* Ability to disable the relates tab in the fixed widget is now configurable.

[GeorgeHaskett]

Robert,

I am wondering if its possible to create reports or data sheets from results that are returned from the eSearch widget.

I am trying to figure out how I can build a data sheet from information that is retrieved using the eSearch widget and temporarly stored within the provided table. The data is being stored somewhere temporarily.

I would like to create a data sheet or report tool/widget or link that obtains its information from the eSearch tool and can be displayed on command via a link. I have seen similar style documents/reports created and used in JavaScript maps.

The data sheet would have various values arranged from the associated table along with a mini map of the feature in question.

Can this be done with Flex and the eSearch?

Where exactly is the data from the eSearch table stored?

Can I access it and use it to make a data sheet?

Thanks,

Haskett

[SladeBridges]

Slade,

   In your widget results do you see the binoculars? Like this?
[ATTACH=CONFIG]20626[/ATTACH]

robert,
yes, i see the results in the widget with the binoculars. the map is not displaying them until i get to a scale in which the layer searched on is visible.
Slade

[RobertScheitlin__GISP]

Slade,

   I am still struggling with why you are experiencing this issue. I have had no other reports of any issue close to this. Can you try and add the new symbology tag to your layers?

            <symbology>
                <picturemarkersymbol url="assets/images/i_search.png" height="30" width="30" xoffset="0" yoffset="0" />
            </symbology>

[RobertScheitlin__GISP]

All,

   Another update is released:

Version 3.1.3 - 1/11/2013
* Fixed some issues with relates and uniquevalsfromfield when using tokens.
* Fixed some issues if the layers url contains the token.

[DanMiller]

Hi Robert,

When using the Graphical Search (I noticed this in your linked site - http://gis.calhouncounty.org/FlexViewer3.1/index.html?config=config-eSearch.xml&esearch=2&slayer=3&e... for Road Centerlines, as well as my own testing), after the Results are shown, if you try to click on the map then it will draw another shape instead of allowing the user to click on one of the highlighted search results on the map.  Not sure if it's just a config issue?

The second issue I noticed is that if you clear a search, do another Graphical Search with Add to Current Selection selected, then it will cause an Error #1009 to appear.  I also tested this using your Road Centerlines.

Dan

[RhettZufelt]

Hi Robert,

When using the Graphical Search (I noticed this in your linked site - http://gis.calhouncounty.org/FlexViewer3.1/index.html?config=config-eSearch.xml&esearch=2&slayer=3&e... for Road Centerlines, as well as my own testing), after the Results are shown, if you try to click on the map then it will draw another shape instead of allowing the user to click on one of the highlighted search results on the map.  Not sure if it's just a config issue?

Dan

try setting this to false in the eSearchWidget.xml:

<keepgraphicalsearchenabled>false</keepgraphicalsearchenabled>


R_

[RhettZufelt]

Robert,

Don't know if this helps with the 1009 error, but I can reproduce, but with 3.1.2 I do not get the error AND it makes the selection.  However, it does not send the data to the fixed datagrid.

If I create new selection it populates the DG, then add to it and it gets added to the DG.  Just the selected features don't populate the grid when "add to" selection is chosen and no selection exists.

Maybe this helps narrow it down,

R_

[RobertScheitlin__GISP]

Rhett,

   Thanks that did narrow it down and I now have it resolved and the fix will be in 3.1.4.

[RobertScheitlin__GISP]

Dan,

   As Rhett suggested your fist issue is a configuration issue. Thanks for reporting the 1009 error.

[DanMiller]

Dan,

   As Rhett suggested your fist issue is a configuration issue. Thanks for reporting the 1009 error.

NP Robert.  I'll test that out, haven't had time to test your latest version of eSearch (3.1.3) yet - I have to upgrade today from 3.1.2. The 1009 error was something that I noticed when trying to configure my own eSearch xml to look like your sample version.

One thing I'm still a little fuzzy on is how the Relates and Tables types work differently from the layer types so trying to do some testing to get a better understanding.  I had been working with an older version of eSearch that only used layers + definition expressions in the XML, so trying to get caught up with the latest features.  Thanks again for all of your work.