nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Enhanced Search Widget for FlexViewer 2.1

RobertScheitlin__GISP

All Here is my next widget in the FlexViewer 2.1 series

Special thanks to Erwan Caradec for contributing to this code.

The Enhanced Search Widget extends the standard search widget with a floating data grid and a new spatial query w/buffering.

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

Find more posts tagged with

Accepted answers

All comments

RobertScheitlin__GISP

All,

Version 2.2.5 now available.

Version 2.2.5 - 01/19/2011
* Added the ability to use coded value domain values in a combobox instead of typing in a text input box.
* Added configuration option to disable certain titlebar buttons.
* Added configuration option to set the default search option on widget load i.e. text, graphical, or spatial
* Added configuration option to add a pixel tolerance to the graphical point search for point on point searches.
* Documentation pdf for the configuration file is now added.

RobertScheitlin__GISP

David,

Line search tolerance was going to involve a buffer operation which meant a round trip to the server and more time to do the search. So I opted to not do that. 2.2.5 will act much like identify as far as adding a configured amount of screen pixels to the search when using a graphical point search. I think you were the second to ask about this so when more than one person asks for something and it makes sense than I try to add it.

DavidAllen

Wow, you are absolutely amazing. Your dedication is much appreciated and I will look forward to the new version.

And I second that! As I learn more about Flex coding, I gain a greater appreciation for your efforts!

David Allen

JimWelsh

Wow, you are absolutely amazing. Your dedication is much appreciated and I will look forward to the new version.

RobertScheitlin__GISP

Jim,

Hopefully version 2.2.5 will come out today and it will have all of this configurable.

i.e disablebuttons, defaultselectionoption, toleranceforpointgraphicalselection, text search by selecting from valid domain values in a combobox when this option is set in config.

If you need it fixed right away then the code change would be:

<viewer:BaseWidget xmlns:esri   ="http://www.esri.com/2008/ags"
       xmlns:fx    ="http://ns.adobe.com/mxml/2009"
       xmlns:s    ="library://ns.adobe.com/flex/spark"
       xmlns:mx    ="library://ns.adobe.com/flex/mx"
       xmlns:mxeffects      ="com.adobe.ac.mxeffects.*"
       xmlns:viewer         ="com.esri.viewer.*"
       xmlns:Search        ="widgets.eSearch.*"
       x="600" y="300"
       currentState="textInput"
       widgetConfigLoaded="init()">
 <viewer:states>
  <s:State name="graphicalInput"/>
  <s:State name="textInput"/>
  <s:State name="spatialInput" />
  <s:State name="resultsList"/>
 </viewer:states>

Use one of the other State names instead.

JimWelsh

Robert,

Thanks for the info, it was exactly what I was expecting. The link is removed as I wanted, but the text search still loads by default when the widget is opened. Where is the best place to change the default search?

Thanks again.

RobertScheitlin__GISP

Jim,

Currently there is no configuration change to disable those but That would be an easy add for the next release. Currently you would have to comment out these lines:

if (configSearchText.length)
     wTemplate.addTitlebarButton(ICON_URL + "i_searchtext.png", textsearchLabel, showStateTextSearch);

DavidAllen

David,

Nope no tolerance setting for them. As you can see on my preview site there isn't an issue with point or line selection. http://gis.calhouncounty.org/IdentExample/index.html?config=config-eSearch.xml

Are you trying to select points using point or line? if so you are HIGHLY unlikely to click in the precise location to get a result.

Yep - point on point selection. That must be why it's not working. I think I can transfer the point location of headstones to a polygon showing the burial site and then it will work with a point selection.

RobertScheitlin__GISP

David,

Nope no tolerance setting for them. As you can see on my preview site there isn't an issue with point or line selection. http://gis.calhouncounty.org/IdentExample/index.html?config=config-eSearch.xml

Are you trying to select points using point or line? if so you are HIGHLY unlikely to click in the precise location to get a result.

JimWelsh

Robert,

As always, your work is fantastic. Quick question...

What is the easiest way to disable specific search types? i.e. disable the text search function

Thank you.

DavidAllen

Is there a search sensitivity for the Graphic Selection "Select by Point" or "Select by Line"? I've got the rectangle and polygon selections working great, but even if I zoom way in I can't get the point or line to select anything.

RobertScheitlin__GISP

Eric,

I have been studying your xml and don't see any issue so what I would do is remove all the other fields from the fields list except SUB_NAME and see if that eliminates the error. If it does add the fields back one by one to try and narrow down what the issue is.

EricVenden

Thanks Richard,

Here's the info in the layer tag:

        <layer>
            <name>Subdivisions by Name</name>
            <url>http://arcgis-srv1.village.gurnee.il.us/ArcGIS/rest/services/Subdivisions/MapServer/1</url>
            <expressions>
    <expression alias="SubdivisionSearchByName" textsearchlabel="Search by Name [ Example: Southridge ]:">SUB_NAME LIKE '%[value]%'</expression>
            </expressions>
   <graphicalsearchlabel>Use one of the graphical search tools to select Subdivisions</graphicalsearchlabel>
   <spatialrelationlayer>true</spatialrelationlayer>
            <titlefield>SUB_NAME</titlefield>
            <linkfield linkprefix="" linksuffix=""></linkfield>
   <icon isfield="true" iconprefix="" iconsuffix=""></icon>
            <fields all="false">
    <field name="SUB_NAME" alias="Subdivision Name" gridfield="true"/>
    <field name="SUB_PHASE" alias="Phase" gridfield="true"/>
    <field name="SUB_UNIT" alias="Unit" gridfield="true"/>
    <field name="DOC_NUM" alias="Doc Number" gridfield="true"/>
    <field name="PLAT_PDF" alias="Subdivision Plat PDF" gridfield="true"/>
    <field name="OBJECTID" alias="ObjectID" gridfield="true"/>
            </fields>
   <zoomscale>1200</zoomscale>
        </layer>

RobertScheitlin__GISP

Eric,

You need to post your SearchWidget.xml as error 1009 is a very generic error you get when something is null, so that information is not much use in diagnosing the issue.

EricVenden

Looking for some help on the eSearch widget 2.2.4 in Flex Viewer 2.2.

I am getting a #1009 error when running a particular search. If I click on the Data Grid icon, I get the proper results in that window. It is a simple query on a layer that does not contain joins. Here's the SQL: SUB_NAME LIKE '%[value]%' The query must be running properly as the results in the Data Grid are correct...

Any ideas?
Thanks
Eric Venden
GIS Coordinator
Gurnee, IL

RobertScheitlin__GISP

David,

There is a reason you do not see any examples of esri or anyone else doing this in their code. The reason is that Adobe does not guarantee the order of objects in an ArrayCollection as you parse thought the results. So as the results of the search widgets uses an array collection there is no guarantee to the order of the results. You can sort the results but it has to be done in code.

DavidAllen

David,

The enhanced search widget displays results in the widget results, the info popup and a floating data grid if you configure it for that. So the gridfield only attribute says don't display it in the info popup or widget results, only the floating data grid.

That certainly makes sense. I haven't configured everything so I haven't seen the data grid yet.

What about sorting the results, though?

RobertScheitlin__GISP

David,

The enhanced search widget displays results in the widget results, the info popup and a floating data grid if you configure it for that. So the gridfield only attribute says don't display it in the info popup or widget results, only the floating data grid.

DavidAllen

Robert - here's another question. Can you explain what the field attribute setting gridfield and gridfieldonly do? I'm seeting gridfield to true and false on different fields, but they all still show up in both the search results display and the pop-up box. I've tried setting gridfieldonly to true, and then the field doesn't show up in either the search results or the pop-up box.

Am I using these correctly?

            <fields all="false">
             <field name="First_name" alias="First name" gridfield="false"/>
             <field name="Middle_nam" alias="Middle name" gridfield="true"/>
                <field name="Last_name" alias="Last name" gridfield="true"/>
                <field name="B_month" alias="Birth - Month" gridfield="true"/>
                <field name="B_day" alias="Birth - Day" gridfield="true"/>
                <field name="B_year" alias="Birth - Year" gridfield="true"/>
                <field name="D_month" alias="Death - Month" gridfield="false"/>
                <field name="D_day" alias="Death - Day" gridfield="false"/>
                <field name="D_year" alias="Death - Year" gridfield="false"/>
                <field name="Comment" alias="Comment" gridfield="false"/>
                <field name="Comment_2" alias="Comment" gridfield="false"/>
                <field name="age" alias="Age at time of death" gridfieldonly="true"/>
            </fields>

DavidAllen

OK - rookie question ...
I've gotten everything working, but I want to order the results of the queries. So I added the Order By command to the end of my query like this:
<expression alias="Last name" textsearchlabel="Search for last name [ Example: Fuller ]:">upper(Last_name) like upper('%[value]%') ORDER BY "First_name"</expression>

The query runs without errors, but the output isn't ordered by the first name. Any tips here?

David Allen

LisaArnold

Hmm... not sure. If I put semicolons in both places I get the RPC fault error. I'm going to have to tell my users how to write their queries, so I can give examples with colons, but if some users are familiar with the XML escape code it could be confusing. Let me know if you think of any reasons why it might be working like this for me.

Thanks again,
Lisa Arnold

RobertScheitlin__GISP

Lisa,

Strange that that worked for you. I did mistype but it is actually suppose to be the other way around. ampersand gt semicolon and ampersand lt semicolon. That is the XML escape code for > and <.

LisaArnold

Got it, though in case anyone uses this post for reference I had to change the syntax slightly.

FieldYr &gt:= 2003 AND FieldYr &lt:= 2005

Notice a colon after both gt and lt instead of a semicolon after gt.

Thanks!
Lisa Arnold

RobertScheitlin__GISP

Lisa,

You have to escape the greater than and less than symbols as these are kind of commands in xml language. So you have to type:

FieldYr &gt;= 2003 AND FieldYr &lt;= 2005

so that the xml parser does not interpret then as something else

LisaArnold

One other thing Robert - I know you said somewhere that any SQL statement could be used in the search. I want to search a field with different years in it, for example: FieldYr >= 2003 AND FieldYr <= 2005

If I type that in the search box I get the RPC fault error. Since it already knows to search the field FieldYr, I tried: >= 2003 AND <= 2005 This also produces the error.

Can you please give an example of the proper syntax here?

Thank you,
Lisa Arnold

LisaArnold

Yep, that worked. Something I should have know really. Thanks for reminding me.

Lisa Arnold

RobertScheitlin__GISP

Lisa,

The solution is quite simple:

<expression alias="FieldYr" textsearchlabel="Search Field Year [ Example: 2003 ]:">FieldYr = '[value]'</expression>

The above SQL expression is for when FieldYr is a string. Here is what you need because its a number:

<expression alias="FieldYr" textsearchlabel="Search Field Year [ Example: 2003 ]:">FieldYr = [value]</expression>

Notice no single quotes (which are for string) around the [value]

LisaArnold

Hello all,

I am getting the error below when I try to search on any number fields, searching on text fields works just fine. I am using version 2.2.3.

Error: RPS Fault faultString="Unable to complete operation." faultCode="400" faultDetail="Unable to complete query operation."

Here are my expression lines from SearchWidget.xml
<expression alias="FieldYr" textsearchlabel="Search Field Year [ Example: 2003 ]:">FieldYr = '[value]'</expression>
<expression alias="FieldStatus" textsearchlabel="Search Field Status [ Example: Active ]:">upper(FieldStatus) = upper('[value]')</expression>

Any ideas?

And a side note, thanks for the awesome widget Robert!

Lisa Arnold
University of New Mexico

TimHoward

Robert,

You da man..as usual!! Thanks so much.

RobertScheitlin__GISP

Tim,

Bug is fixed in latest version 2.2.4

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.