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

Trouver plus de publications taguées avec

Accepted answers

All comments

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,

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.

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

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

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,

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.

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.

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.

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.

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

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);

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,

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

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

imsolost_0-1729025696982.png

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

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.

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.

JohnGregorovic

Robert,

Thank you for all of your hard work and also the patience it takes to follow up with everyone's emails

EricVenden

Good afternoon Robert,

I tried what you suggested and I still get the same error. I have updated to your latest version 2.2.5 and still get the same error...any other ideas.

Thanks
Eric

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.

RobertScheitlin__GISP

Eric,

Have you tried just typing your url: http://arcgis-srv1.village.gurnee.il.us/ArcGIS/rest/services/Subdivisions/MapServer/1 in the address bar of a browser and clicking the query link and adding

SUB_NAME LIKE '%Southridge%'

to the where box and * in the outfields to see if it works in the REST services directory?

EricVenden

Robert,
Thanks for the suggestion - this works fine..the query returns results. The grid view in the flex app does show the proper results, it's just the "initial" window that only displays the Error message.
Eric

RobertScheitlin__GISP

Eric,

OK, you are the only one reporting having an issue like this so I need you so continue to help me diagnose this issue as it must be specific to your data or configuration some how. Do the same thing that I asked you to do last time but instead out putting * for the outfields this time specify the fields
SUB_NAME,SUB_PHASE,SUB_UNIT,DOC_NUM,PLAT_PDF,OBJECTID

EricVenden

Robert,
If I enter:       like '%southridge%'
The query will not run (I get an "Unable to perform query" message).

If I enter:        southridge
I get all records LIKE southridge and the proper return fields (specifying * or certain fields).

If I enter:       %southridge%
I get "No Results Found"

I'm familiar with sql, but not quite sure how select statements are parsed in REST services.
Additionally, how is the query field determined? Does it use the first text field for a feature class?
See attached
Thanks Robert

sub_query.PNG

RobertScheitlin__GISP

Eric,

Try adding:

SUB_NAME LIKE '%Southridge'

in the Where box not the top box that you are questioning about. The field that you are asking about is determined by the display field in ArcMap for that particular layer. So in ArcMap if you go to the layer properties and then display tab you will see (in v10) Display Expression then field. What this means is a published map service is that field is used as

Shorthand for a literal search text on the display field, equivalent to: where YourDisplayField like '%SearchText%'.

The search expression of '%something%' means that you are expecting any number of character in front of and after the something string. So if your SUB_NAME field has the exact value of "Southridge" than there is no need for the like and wildcards.

EricVenden

Robert,
The results are returned properly by entering a valid where clause and using the * or specifying the fields to be returned.

Eric

EricVenden

Robert,
Not sure if this is helpful, but if I enter a value that I know will not return results, the widget returns "Features Selected: 0"...

Eric

RobertScheitlin__GISP

Eric,

I got to say I am stumped then. I can not duplicate the error so it is hard to say what is going wrong. Last chance effort... Can you do the query again on the REST services directory page using the where box and specifying the fields and change the format at the bottom of the page to JSON then when you get the results highlight them and copy and paste them into a text file and attach that text file to a post for me to review?

EricVenden

Robert,
There are numerous null values in the data (in the SUB_NAME field)....let me edit these values and see if this does the trick. Is this a possibility?

Thanks
Eric

RobertScheitlin__GISP

Eric,

That shouldn't be an issue but give it a try.

EricVenden

Robert,
See attached txt file - query string was: SUB_NAME LIKE '%victorian%'

Thanks
Eric

Sub_Search_Victorian.txt.zip

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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