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

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

RobertScheitlin__GISP

Eric,

I think we are running into an issue here. To properly diagnose the issue we need certain things to remain constant in the debug process. So try the query again using this where clause:

SUB_NAME LIKE '%Southridge%'

and these outfields:

SUB_NAME,SUB_PHASE,SUB_UNIT,DOC_NUM,PLAT_PDF,OBJECTID

EricVenden

Robert,
See attached with the search criteria, etc as you had specified.

Thanks
Eric

Sub_Search.txt.zip

RobertScheitlin__GISP

Eric,

So for testing purposes plug this exactly into your SearchWidget.xml file and be sure to clear your browsers cache and try the query again.

  <layer>
   <name>Subdivisions by Name</name>
   <url>http://arcgis-srv1.village.gurnee.il.us/ArcGIS/rest/services/Subdivisions/MapServer/1</url&gt;
   <expressions>
    <expression alias="Subdivision Search By Name" textsearchlabel="Search by Name [ Example: Southridge ]:" >SUB_NAME = '[value]'</expression>
   </expressions>
   <graphicalsearchlabel>Use one of the graphical search tools to select Subdivisions</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>SUB_NAME</titlefield>
   <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>
   <linkfield></linkfield>
   <icon isfield="false"></icon>
   <zoomscale>1200</zoomscale>
  </layer>

EricVenden

Robert,

I used the code you sent and the initial search popped the #1009 error, but the results grid displays the correct information. I used "Southridge" as the search string.

see attached
Thanks
Eric

sub_search_result1.PNG

RobertScheitlin__GISP

Eric,

Maybe we are trying to look to narrowly at this... Post your whole SearchWidget.xml

EricVenden

Here it is Robert,
I copied the xml from a search that we have working and tweaked it.
Thanks
Eric

SearchWidget.xml.txt.zip

RobertScheitlin__GISP

Eric,

Try using this 2.2.5 version of the xml with your data plugged in for you.

SearchWidget.xml.txt.zip

EricVenden

Robert,
I tried the new xml with the same result.
Eric

RobertScheitlin__GISP

Eric,

As long as you cleared your browser cache to ensure that the new xml was used. I am completely out of ideas.

EricVenden

No problem Robert - I've taken enough of your time. ...it's a head scratcher. I have 4 other searches that work fine.

If I stumble on something that fixes it, I'll let you know.
Thank you
Eric

TonyBlades

Robert, Eric,
I'm having the same issue. I have other searches working but in this case what I think my problem is is that not all of the records have a spatial reference to the layer. Could that be it?

tb

RobertScheitlin__GISP

Tony,

Can you elaborate on that?

I think my problem is is that not all of the records have a spatial reference to the layer

Are you saying that a particular feature class in your map document is unprojected and has no spatial reference?

TonyBlades

Robert,
I have a layer with 5 maintenance area polygons, symbolized by cost center. When I found out I couldn't make a 1-M join work, I added my 40 maintenance employees to the maintenance area table and assigned each of them to one of the cost centers. Now when I search by cost center I get the 1009 error on the search box but on the grid table each of the employees in that cost center show up with their coorisponding field data.
In my map document when I select one of the employees, the area he's assigned to is not selected. My original 5 records defining the maintenance areas are still in the table and when those records are selected, of course the polygon is also selected.

tb

MelissaJohnson

Eric,

This is a shot in the dark, but it may be the issue you are having. I too could not get my results to pull up and I found that it was because the search was case sensitive. The data in my underlying table was all caps. The fix was to use upper (for example):

<expression alias="Owner Name" textsearchlabel="Search By Owner Name...(Last Name, First Name)" field="OwnerName1" usedomain="true">upper(OwnerName1) LIKE upper('[value]%')</expression>

May not be the solution but worth a shot.
Melissa

IsaiahAguilera

Robert,

This may seem rather elementary but I am using your search widget and it works great. I noticed in your conversation with Eric that he is able to search using "like" words. As of now all of my searches must match the field exactly to return results. Doing this may go beyond the spectrum of this widget but how would I able to search and get results without having to match whats in the field exactly.

e.g. Search "Civic" And Results Give Me "Civic Center Dr"

RobertScheitlin__GISP

Isaiah,

In the zip you have a SearchWidget.xml file that contains an example of this:

   <expressions>
    <expression alias="Traffic Camera Description" textsearchlabel="Search Traffic Cameras by Location... [ Example: I-71 ]">upper(DESCRIPTION) LIKE upper('[value]%')</expression>
   </expressions>

IsaiahAguilera

Robert,

Thank you, I must have deleted that before reading it. Works great. Thank you for all your help.

EricVenden

Thanks for the idea Melissa,

I tried it and the search still errors out on the initial results window. The grid shows the proper results.

Eric V
Gurnee, IL

GeraldLee__GISP

Eric,
I was having the same problems with the query widget (error code #1009). i read an earlier answer from Robert S explaining the need to have at least the OBJECTID and shape field checked visible, when you publish your MXD (or MSD). when i did that and republished, all was fixed. dont know if this is the answer for you but its worth a shot anyway..
Gerald

LisaArnold

I am using the linkfield element to enabling linking to pdf files. My linkfield 'RptLink' contains only the file name, no path, no extension. When I click on the icon element from the search results, I am successfully linked to the proper pdf file and the address in the browser is correct (http://gis-web.heritage.unm.edu/gpd/reports/04-gtr-264.pdf) If I view my search results in the grid view and I click on the link to the report there, I get a 404 File not found error and I see that the path in the browser is incorrect (http://gis-web.heritage.unm.edu/gpd/04-gtr-264). Please see my search widget configuration below. Anyone see what I'm doing wrong?

            <graphicalsearchlabel>Use one of the graphical search tools to select Field Validation points</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>Source</titlefield>
            <linkfield linkprefix="http://gis-web.heritage.unm.edu/gpd/reports/" linksuffix=".pdf">RptLink</linkfield>
   <icon isfield="true" iconprefix="" iconsuffix=""></icon>
            <fields all="false">
                <field name="SciName" alias="SciName" gridfield="true" gridfieldonly="true"/>
                <field name="FieldYr" alias="FieldYr" gridfield="true"/>
                <field name="FieldStatus" alias="FieldStatus" gridfield="true"/>
    <field name="Seen" alias="Seen" gridfield="true" gridfieldonly="true"/>
    <field name="OtherSpecies" alias="OtherSpecies" gridfield="true" gridfieldonly="true"/>
    <field name="Surveyor" alias="Surveyor" gridfield="true" gridfieldonly="true"/>
    <field name="Source" alias="Source" gridfield="true" gridfieldonly="true"/>
    <field name="FieldNotes" alias="FieldNotes" gridfield="true" gridfieldonly="true"/>
    <field name="RptLink" alias="RptLink" hyperlinkgridfield="true" gridfieldonly="true" hyperlinkaliastext="View report"/>
    <field name="SourceShape" alias="SourceShape" gridfield="true" gridfieldonly="true"/>
    <field name="ObsLocation" alias="ObsLocation" gridfield="true" gridfieldonly="true"/>
    <field name="FieldDate" alias="FieldDate" gridfield="true" gridfieldonly="true"/>
    <field name="POINT_X" alias="POINT_X" gridfield="true" gridfieldonly="true"/>
    <field name="POINT_Y" alias="POINT_Y" gridfield="true" gridfieldonly="true"/>
    <field name="State" alias="State" gridfield="true" gridfieldonly="true"/>
    <field name="County" alias="County" gridfield="true" gridfieldonly="true"/>

Thanks,
Lisa Arnold
University of New Mexico

RobertScheitlin__GISP

Lisa,

You are missing the link prefix and suffix here:

<field name="RptLink" alias="RptLink" hyperlinkgridfield="true" gridfieldonly="true" hyperlinkaliastext="View report" linkprefix="http://gis-web.heritage.unm.edu/gpd/reports/" linksuffix=".pdf"/>

LisaArnold

Great thanks, I wasn't recognizing the functionality of the linkfield element as separate than the field attributes.

Why though in the gird view does it always put the hyperlinked field last?

Thanks,
Lisa Arnold
University of New Mexico

RobertScheitlin__GISP

Lisa,

Currently that is just one of those FEATURES of the widget...

EricVenden

Gerald,

That was it!!!..I had OBJECTID and Shape fields unchecked in the mxd.
Thanks very much.

Eric V
Gurnee, IL

RobertScheitlin__GISP

Thanks Gerald!

Eric,

sorry sometimes I forget to look for the simple things.

EricVenden

No problem Robert..I should have looked at that..had issues in the past with IMS relating to that.

Robert - Can results be sorted?

Thanks
Eric

GeraldLee__GISP

Eric,
Very cool. glad i could help someone for a change. Usually its the other way around..
Gerald

btw--Please dont say IMS. i get nauseous.

RobertScheitlin__GISP

Eric,

In the Floating Data Grid yes just use the column header to sort.

EricVenden

Robert,
I tried clicking the column header in the floating grid - it does not sort the column. I looked at the documentation - is there a config for this in the xml or is it "built-in"?

Thanks
Eric

RobertScheitlin__GISP

Eric,

This is standard Flex Data Grid functionality. Try double clicking.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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