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 Part III

RobertScheitlin__GISP

All,

Here is a new thread to post questions and discuss the Enhanched Search Widget. The old thread was getting too long.

Find more posts tagged with

Accepted answers

All comments

AngieAllison

Marie,

So in Version 3.0 there is some issue you are going to have to work around. You need to use uniquevalsfromfield instead of domain as using domain in 3.0 will force you to have a value for each domain field. The next issue you will have to Just deal with in version 3.0 is that once you have chosen a value from the dropdown list the search will automatically be executed (this was fixed in latter releases). I am going to assume that your diameter field is numeric and not a string and I adjusted your expression for that assumption.

Here is a corrected configuration for your layer:

        <layer>
            <definitionexpression></definitionexpression>
            <enableexport>true</enableexport>
            <name>Water Mains</name>
            <url>http://gis-01/ArcGIS/rest/services/MAP_DOCS/dmww_water_server/MapServer/23</url&gt;
            <expressions>
                <expression alias="Material,Diameter and Install Date" textsearchlabel="Search Material:" isvaluerequired="false">
                    <values>
                        <value prompt="Material" uniquevalsfromfield="MATERIAL" isvaluerequired="false">MATERIAL = '[value]'</value>
                        <value prompt="Diameter" uniquevalsfromfield="DIAMETER" isvaluerequired="false" operator="AND">DIAMETER = [value]</value>
                        <value prompt="Example: 01/01/2007 Install Date" isvaluerequired="false" operator="AND">INSTALLDATE >= date '[value] 00:00:00'</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Water Mains</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>FACILITYID</titlefield>
            <fields all="false">
                <field name="DIAMETER" gridfield="true" />
                <field name="FACILITYID" gridfield="true" />
                <field name="MATERIAL" gridfield="true" />
                <field name="INSTALLDATE" gridfield="true" dateformat="MM/DD/YYYY" useutc="true" />
            </fields>
            <links/>
            <zoomscale usegeometry="true" zoompercent="1.6"></zoomscale>
            <autoopendatagrid>false</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates/>
            <symbology>
                <simplelinesymbol color="0x00ff00" alpha="0.8" width="2" />
            </symbology>
        </layer>

Also - the date value that you changed?? i am trying to do a greater than or equal to on the date and it seemed to be working the way i had it. is it wrong?? Is it possible to do a "between" dates ??

MATTHEWPORTER

Are there any issues when using a attribute field with a coded domain. I get an error 400 when i do a search.

                <expression alias="Access Status" textsearchlabel="Search Access Status:">
                    <values>
                        <value userlist="Property Acquired,Est. Access Date Exceeded">AquisitionCode = '[value]'</value>
                    </values>
                </expression>

I am thinking that = '[value]' should be something else like domain?

Thanks!

Matt

RobertScheitlin__GISP

Marie,

If you had the date working before than leave it the way you had it. Doing a date range is quite a bit more difficult. You can do it but you would have to hard code one of the dates or use two expressions values. You should do your SQL expression testing in ArcMap to figure out the exact language.

RobertScheitlin__GISP

Matt,

Using a coded domain in the expression would not look like what you have... That is a userlist. Are you asking how to use a domain field? If so that would look like this (assuming that the field is type string):

<value prompt="Material" field="MATERIAL" usedomain="true" isvaluerequired="false" autosubmit="false" >MATERIAL = '[value]'</value>

MATTHEWPORTER

Thanks Robert!

I am asking how to use a domain field. But the field type is not string. It is numeric, short type.

I currently have

                 <expression alias="Access Status" textsearchlabel="Search Access Status:">
                    <values>
                        <value field="AquisitionCode" usedomain="true">AquisitionCode = '[value]'</value>
                    </values>
                </expression>
When I take the selection action it returns --- faultcode=400 faultdetail=""
Is there something differant for short type?

RobertScheitlin__GISP

Matt,

Yes when querying numeric field you do not wrap the [value] in single quotes.

<value field="AquisitionCode" usedomain="true">AquisitionCode = [value]</value>

MATTHEWPORTER

Bam!

Your awesome! That was it.

Thank You!

AngieAllison

Also - the date value that you changed?? i am trying to do a greater than or equal to on the date and it seemed to be working the way i had it. is it wrong?? Is it possible to do a "between" dates ??

Ok Robert I am in process of updateing all my widgets and Flex Viewer to 3.3 so i can use the full capability of this widget. i still am not able to have 2 queries with domain values. I am taking the date out for now just to eliminate that problem so here is the piece of the xml
   <expressions>
    <expression alias="Material" textsearchlabel="Search Mains:" isvaluerequired="false" autosubmit="false">
     <values>
      <value prompt="Material" field="MATERIAL" usedomain="true" isvaluerequired="false" autosubmit="false" >MATERIAL = '[value]' </value>
      <value prompt="Diameter" field="DIAMETER" usedomain="true" isvaluerequired="false" autosubmit="false"operator= "AND" > DIAMETER = [value] </value>
      
     </values>
     </expression>
    </expressions>
and attached is a picture of my widget.
see how it is auto filling in the data? i would think they would need to start out blank?? I dont understand what i have done wrong here.

Doc11.docx

RobertScheitlin__GISP

Marie,

Go get Version 3.3.1 (posted a few minutes ago) it relsoves that issue.

HudsonSmith

I am having problems with getting my fixed datagrid widget to work in conjunction with my esearch widget. Any ideas? I followed the Enhanced Search Widget Fixed Datagrid Setup pdf. and my search results box is on my widget but when I perform an enhanced search no results popup in the datagrid?

AngieAllison

Thanks Robert i will try it.

RobertScheitlin__GISP

Hudson,

So are you saying that you see the fixed datagrid at the bottom of your app but that it does not get populated with your search results?..

Following the Enhanced Search Widget Fixed Datagrid Setup pdf will get you going as far as adding the widget but you will have to configure which field go to the datagrid in the eSearchWidget.xml based on the guidance from the Enhanced Search Widget XML Configuration.pdf or looking at the examples in the default eSearchWidget.xml in the download.

AngieAllison

When i do the export to text it does not come out right so that i can Import into Excel. It's like the seperators don't come out correctly or something?
attached is the text file, the csv fiel and a word doc showing excel.
i had to change the csv file to .doc to get it to upload.

Selected Records.doc.zip

This is the text example.docx

Selected Records.txt.zip

RobertScheitlin__GISP

Marie,

The fact that your data has 2" the double quote is throwing excel for a loop... Normally the " is used as a text qualifier and the fact that your data looks like "2"","26007887", etc, etc it is an issue for excel. In excel if you set the Text Qualifier to none than you will see how it is suppose to work minus the double qoutes wrapping each column.

HudsonSmith

Robert,

Okay I realized it works when I <fields all="false> and then specify my specific fields but I would like all fields to display in the results. Here is my code for this part. Let me know if you see something wrong. Thank you.
<spatialsearchlayer>false</spatialsearchlayer>
            <titlefield>ZONING_NAME</titlefield>
            <fields all="true"/>
            <links/>
            <zoomscale usegeometry="true" zoompercent="2"/>
            <autoopendatagrid>false</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates/>

RobertScheitlin__GISP

Hudson,

You can not do it that way. If you want field in the datagrid then you have to define them in the XML.

HudsonSmith

Robert,

Alright I understand Thank you for your help!

CaseyMcMillin

Casey,

OK, finally I am able to see your configuration issue. I am expecting a zoomscale tag in your relate tag. As indicated in red below and you need to remove or change the symbology tag you have (which is now for a Polygon and your layer is a PolyLine), Your FacilityID field is a numeric field so your expression should not wrap the [value] in single quotes (which is the way you do for strings). The same goes for your Diameter field expression. It is normally little attention to detail things like this that trip people up. In the Next version I will do some better error traping for things like the missing zoomscale tag.

        <layer>
            <token />
            <definitionexpression />
            <enableexport>true</enableexport>
            <name>Sanitary Main</name>
            <url>http://GIS01.lebanon.local:6080/arcgis/rest/services/OperationalLayers/Utilities/MapServer/3</url&gt;
            <expressions>
                <expression alias="Facility ID" textsearchlabel="Search Specific Main:" isvaluerequired="false">
                    <values>
                        <value prompt="Example: 1032" isvaluerequired="false">FACILITYID = [value]</value>
                    </values>
                </expression>
                <expression alias="Attributes" textsearchlabel="Search Mains:" isvaluerequired="false">
                    <values>
                        <value prompt="Type:" isvaluerequired="false" uniquevalsfromfield="TYPE" autosubmit="false">TYPE = '[value]'</value>
                        <value prompt="Diameter:" isvaluerequired="false" uniquevalsfromfield="DIAMETER" autosubmit="false" operator="AND">DIAMETER = [value]</value>
                        <value prompt="Material:" isvaluerequired="false" uniquevalsfromfield="MATERIAL" autosubmit="false" operator="AND">MATERIAL = '[value]'</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Main</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>Sanitary Main</titlefield>
            <fields all="false">
                <field name="FACILITYID" gridfield="true" />
                <field name="TYPE" gridfield="true" />
                <field name="DIAMETER" gridfield="true" />
                <field name="MATERIAL" gridfield="true" />
                <field name="YEARBUILT" gridfield="true" />
                <field name="EDITDATE" gridfield="true" />
                <field name="INSPECTIONDATE" gridfield="true" />
            </fields>
            <links />
            <zoomscale usegeometry="true" zoompercent="2" />
            <autoopendatagrid>false</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates>
                <relate id="0" label="Asbuilts" enableprintgrid="false">
                    <fields all="false">
                        <field name="ASBUILTID" />
                        <field name="FILEPATH" hyperlinkgridfield="true" hyperlinkaliastext="View Asbuilt" linkprefix="http://GIS01/Asbuilts/" linksuffix=".pdf" />
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
            </relates>
            <symbology>
                <simplefillsymbol color="0xff0000" alpha="0.5">
                    <outline color="0xff0000" alpha="0.8" width="2"/>
                </simplefillsymbol>
            </symbology>
        </layer>

Robert,
Thank you very much for your assistance. You have already gone above and beyond trying to help with the relationship errors I am having. I made the changes you listed, but interacting with the fixed data grid still causes errors. I think we are on the right track with the relate zoom scale, but I have tried multiple values there and nothing seems to change the result.
Thanks,
Casey

RobertScheitlin__GISP

Casey,

I was able to debug using the data you provided and narrow it down to the two main issues I told you about in my last post. The zoom scale I provided in red and removing the polygon symbology tags or better yet changing them to the proper polyline symbology:

            <symbology>
                <simplelinesymbol color="0x00ff00" alpha="0.8" width="2" />
            </symbology>

Fixed the issues for me. Can you try publishing the same data you sent me and configure it and see if you can get the same positive results I am getting? That way we can narrow things down more.

AngieAllison

Marie,

The fact that your data has 2" the double quote is throwing excel for a loop... Normally the " is used as a text qualifier and the fact that your data looks like "2"","26007887", etc, etc it is an issue for excel. In excel if you set the Text Qualifier to none than you will see how it is suppose to work minus the double qoutes wrapping each column.

ok thank you for all your hard work on these widgets

RobertScheitlin__GISP

Marie,

In the next release you will be able to specify the Text Qualifier in the eSearchWidget.xml and this would allow you to use a single quote instead of a double and that would help for your data having the double quote in it for inches.

BenScott1

Hi,

I am trying to configure a search on three fields. It seems that whatever I set 'isvaluerequired' to (true or false), a value must be entered in every text box before the search button is enabled and every box has a red asterisk indicating value required.

In the 'Road Name and Zip Code' search in the example viewer, which is similar to the search I am trying to configure, it is possible to search after entering a value in only one of the three boxes.

Am I changing the correct config item? I have tried setting 'isvaluerequired'=false at both the expression and value level but with no change.

Relevant config text below.

Cheers, Ben.

           <expressions>
                <expression alias="Lot, Section and Plan" isValueRequired="false" textsearchlabel="Enter any combination of Lot, Section and/or Plan number">
                    <values>
                        <value prompt="Example: 1" isValueRequired="false">upper(lotnumber) like upper('%[value]%')</value>
                        <value prompt="Example: A" isValueRequired="false" operator="AND">upper(sectionnumber) like upper('%[value]%')</value>
                        <value prompt="Example: 36201" isValueRequired="false" operator="AND">plannumber = [value]</value>
                    </values>
                </expression>
            </expressions>

sofialoulad

when i add the url to showdatagrid i get error #1010
😞

RobertScheitlin__GISP

Ben,

Here is the xml configuration for the sample layer you mentioned:

                <expression alias="Road Name and Zip" textsearchlabel="Search by Road Name and Left Zipcode and Right Zip:" isvaluerequired="true">
                    <values>
                        <value prompt="Example: ANDREW" isvaluerequired="false">RD_NAME = '[value]'</value>
                        <value prompt="Example: 36201" isvaluerequired="false" operator="AND">ZIP_L = [value]</value>
                        <value prompt="Example: 36201" isvaluerequired="false" operator="AND">ZIP_R = [value]</value>
                    </values>
                </expression>

RobertScheitlin__GISP

Sofia,

when i add the url to showdatagrid i get error #1010

What in the world do you mean?... There is no showdatagrid tag in the XML...

AngieAllison

Marie,

In the next release you will be able to specify the Text Qualifier in the eSearchWidget.xml and this would allow you to use a single quote instead of a double and that would help for your data having the double quote in it for inches.

Thank you Robert. When do you anticipate that release?
i am having another quirky thing happening. I have a field Material that i could not get to run the query and i finally added the quotes to the value and it runs and it is definatley a text field

AngieAllison

Thank you Robert. When do you anticipate that release?
i am having another quirky thing happening. I have a field Material that i could not get to run the query and i finally added the quotes to the value and it runs and it is definatley a text field

omg am i backwards? numbers get the quotes or text gets the quotes?

RobertScheitlin__GISP

Marie,

I don't have an estimated time as I will not be releasing a new version for one small change, I will wait till I have other changes that I determine are significant enough to warrant a new version. What you mean by

i finally added the quotes to the value and it runs and it is definitely a text field

String field always need single quotes in the Query Expression.

AngieAllison

omg am i backwards? numbers get the quotes or text gets the quotes?

so yeah .......... SORRY I was doing them backwards, I'm a dork. Sorry to bother

PatrickWalker

Hello,
I am using the latest compiled eSearch version widget 3.3.1 in a new ArcGIS API 3.3 for Flex site and I am experiencing different results with my searches than when using the previous eSearch version 3.0.4 in an ArcGIS API 3.0 for Flex site. When I search for a polygon or point feature that returns enough points to zoom out to a scale threshold that the feature is not displayed at, the selected features are not showing up on my map. The search results window or the data grid will display the attributes of the features found and you can mouse thru the data and the tooltip window will move around on the map, but not until you zoom in to the scale threshold of the feature you searched on will they be displayed.
Is there something that I missed in upgrading my site and widget to the latest version? In version 3.0.4, when you would search for these same features they would be displayed on the map at any scale beyond the scale threshold that was set on the feature and I am looking for that same functionality so users will see the results immediately without having to zoom in to the scale dependency of that feature. Thanks, and any help would be appreciated.

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.