Select to view content in your preferred language

Enhanced-Search-Widget-for-FlexViewer Part III

179014
776
04-30-2013 03:58 PM
RobertScheitlin__GISP
MVP Emeritus
All,

   Here is a new thread to post questions and discuss the Enhanched Search Widget. The old thread was getting too long.
Tags (2)
776 Replies
RobertScheitlin__GISP
MVP Emeritus
Julie,

    I have seen several situations where relates that have joins were having issue with the related feature geometry being returned. This is something that you can call esri tech support about but not as it relates to the eSearch (they will just say that they don't support custom widgets), but it may be a known bug.
0 Kudos
glennhazelton
Deactivated User
hi Robert,
I hope this the right thread.
i have been working with your esearch widget for years and i love it.
i just moved to the 3.6 version however and i have problem.
the 'show results in grid' icon is not visible.
how do i get it to show up?
thanks
glenn hazelton
FYI
SINCE I POSTED THIS I discovered the reason: I had NOT added the FixedDG to the config file.
all is well now.
glenn.
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Glenn,

    That button is only visible when you are using the Floating Datagrid and NOT the Fixed datagrid.
0 Kudos
MegPeterson
Regular Contributor
Hi all -

I'm perplexed. I'm trying to populate a drop down list in the eSearch widget, but the values returned in the drop down do not include all the values in the field specified. For example, if the values in the field "PARK" include [Rose Park, Cedar Park, Valley Park], only 'Rose' and 'Cedar' (and 'all) are returned in the drop down; 'Cedar' is not listed.

If I allow the user to simply type in the name 'Cedar', the value appears.

Any ideas? I'm using the eSearch widget (3.0 - 3.0.17f) with 10.1. I realize I'm a bit out of date on the code, but hoping to not have to upgrade.... Many thanks.


<expressions>
 <expression alias="Search by Park" textsearchlabel="Choose from the drop down list below">
 <values>
  <value prompt="Example" uniquevalsfromfield="PARK" isvaluerequired="true">Lower(PARK) like Lower('%[value]%')</value>
 </values>
 </expression>  
 <expression alias="Search by Park type" textsearchlabel="">
 <values>
  <value prompt="Example: Hayward Shoreline">Lower(PARK) like Lower('%[value]%')</value>
 </values>
 </expression> 
</expressions>
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Meg,

   From 3.0 to 3.6 of the eSearch there has been LOTS of bug fixes and at least one or two the deal specifically with the uniquevalsfromfield. All I can tell you is to test 3.6.5 of the eSearch and see if it fixes your issue. I can not support a widget version that id 6 minor version behind (not to mention all the sub versions that I can out with in between those minor versions).
0 Kudos
DavidBuehler
Frequent Contributor
I hope this the place to post this particular question.  If not please let me know.

I am using the 3.6.4 version of the enhanced search widget with the 3.6 flex viewer. I have read the documentation and looked over the forums, and have managed to turn off most of the buttons that are unwanted after doing some beta testing with users.  The only thing I cannot seem to find how to disable is the "Do you want to use the Buffer Graphics or the Selection Graphics --> Selection Graphics" button.  The users like the ability to cancel and adjust their buffers so I would like to keep that particular extra confirmation step.  Also, the two methods also produce different results as indicated in the attached picture. The Red is desirable (Buffer Graphics), and the Blue line is not (Selection Graphics).  Did I miss something on what the difference between the two? Is it possible to retain the "Buffer Graphics" button and disable/remove the "Selection Graphics" button?
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
David,

   The eSearch is the most configurable widget out there, but that portion is not configurable. The select by buffer graphic would select the underlying layer based on the option button that you choose i.e intersects, completely contain, etc. The use selection graphic will do the same but submits the existing selected graphic. I am not sure why your parcel to the south get selected, but I would guess that the parcels have a small overlap. I would check your parcel layers topology to see if you have an overlap issue.
0 Kudos
DavidBuehler
Frequent Contributor
Thanks Robert for the quick reply and answers to my questions.  I will definitely look at the topology of the parcels and see if that solves the issue of non-selection.  Thanks for the explanation on what each one does.
0 Kudos
MarciaElam
Deactivated User
Thank you Robert.

Marcia,

   So the way the widget works is that once a search is completed th widget displays the results in the widget results view and when you click on one of those results it will zoom you to that result. If you hve set the layers symbology in the layer tag (as covered in the the extensive pdf documentation), then your symbology for the search results will show as what ever you configured (most of the time people set it to something different than the layers symbology that is already displaying in the map for that layer). If you have made the mistake of providing the wrong symbology type of that layers geometry type (i.e you are search a point layer and you have the layer symbology set to SimpleFillSymbol for a polygon) than it will not draw anything on the map. If you are using the fixed of floating datagrid with the widget than you will also get the option of using the datagrids subselection color (all of this is covered in the pdf and their are examples in the eSearchWidget.xml that is packaged with the widget download).
0 Kudos
BrentFoster
Emerging Contributor
Hi Robert,

When using the URL Search Configuration, when I specify a parameter that cannot be found, instead of returning 'Features Selected: 0', I get "Index '0' specified is out of bounds.'  If I run the same search and enter the well number manually into the esearch widget, it behaves normally.  This only occurs when attempting to pass the parameter thru the URL address.  If I pass a valid parameter thru the URL, the esearch widget works properly and zooms to the selected well.  It only returns the 'out of bounds' error if I pass a parameter that doesn't exist in the feature.  Is there something i'm missing?  Shouldn't it simply return the message 'Features Selected: 0'?

Here is an example of the URL i'm using.

https://gis-prd-01/wellsearch/index.html?esearch=30025368360001=&showdatagrid=true

Thank you for a wonderfully useful tool.
0 Kudos