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

JayGeisen

Upon upgrading my ArcGIS Server to 10.2 yesterday, I noticed that now one of my search expressions (in the eSearch widget) doesn't work. I'm wondering if anyone else has noticed anything like this after upgrading. The SQL query is:

ADDRESS LIKE (replace('[value]%',' ','%')) OR STREET LIKE '%[value]%'

This query allows one to type in "100 Main", for instance, and get the record for "100 S Main St". After the upgrade, I now get the following error when using this search:

[RPC Fault faultString="Unable to complete operation."
faultCode="400" faultDetail=""]

We're still using the same SQL Native Client (2008 R3) on our server machine, for what it's worth. It's strange because this ceased working right after the upgrade. I wouldn't think changing ArcGIS Server would affect how the query works. Any thoughts are appreciated. Thanks.

RobertScheitlin__GISP

Jay,

Have you verified that the layers id number did not change when the upgrade occurred or have to SPECIFICALLY checked that the field names are still the same in the REST service directory?

JayGeisen

I have, Robert. Nothing has changed. In fact, if I change the query to this, I don't get the error.

ADDRESS LIKE '[value]%' OR STREET LIKE '%[value]%'

But then I lose the ability to type in "100 Main" and get "100 S Main St". In this case, the user has to type in "100 S Main" to get the desired record. While not a huge issue, it was working flawlessly before the 10.2 upgrade.

RobertScheitlin__GISP

Jay,

They must have done something in 10.2 to not allow the SQL command 'replace'. I have never used the 'replace' command in my SQL statements so can't be much help. If you are using the source code than you can do this same thing in the code though.

JayGeisen

Thanks, Robert. I am using the source. Care to point me in the right direction, by chance?

RobertScheitlin__GISP

Jay,

Sure, in the eSearchWidget.mxml find the queryFeaturesText function, then look for the block of code like this and add the lines in red:

                if(queryLayer){
                    var query:Query = new Query();
                    var myPattern:RegExp = /\[value\]/g;
                    var expr:String = "";
                    var eVal:String = "";
                    var criteriaFromValue:String;

                    for(var sg:Number = 0; sg < searchGroup.numElements; sg++){
                        sItemVal = searchGroup.getElementAt(sg) as SearchExpValueItem;
                        queryExpr = configSearchText.expr.values[sg].expression;

                        if (queryExpr == "[value]" || queryExpr.toLowerCase().indexOf(" in (") > 0){
                            //meaning an open SQL expression or an SQL with an IN Statement
                            eVal = sItemVal.textValue;
                        }else{
                            eVal = sItemVal.textValue.replace(/'/g,"''");
                        };
                        /*If the expression is an IN Statement and the the value is a string then
                        replace the user defines comma seperated values with single quoted values*/
                        if(queryExpr.toLowerCase().indexOf(" in (") > 0 && queryExpr.toLowerCase().indexOf("'[value]'") > -1){
                            //replace the begining and trailing single qoutes if they exist
                            eVal = eVal.replace(/^'|'$/g, "").replace(/,|','/g, "','");
                        }
                        if (sItemVal.isValueRequired && !sItemVal.hasAValue()){
                            // no value specified so skip this part of where clause
                            continue;
                        };
                        
                        if (queryExpr == "ADDRESS LIKE '[value]%' OR STREET LIKE '%[value]%'"){
                            queryExpr = "ADDRESS LIKE '" + eVal.replace(" ", "%") + "%' OR STREET LIKE '%[value]%'";
                        }

JustinConner

Does anyone know if this problem is fixed in version 3.5? It pretty much stopped my upgrade to 3.4 and I really would like to update soon.

Found a problem. I've got your latest eSearch version and it works great. One problem though is with printing. When printing a parcel that is highlighted using the new print widget the graphic doesn't maintain it's transparency. It works when using the ESRI search widget however.
[ATTACH=CONFIG]25752[/ATTACH] [ATTACH=CONFIG]25753[/ATTACH]
If you want to see for yourself you can view the app at http://gis.co.wood.wi.us/Flex34/index.html

ChadHall

Chad,

Hmm... You have me wondering what you are talking about exactly, because the graphical serach portion of the widget will buffer a point, polyline, rect, or polygon that you draw. The Spatial Search will buffer what ever type of layer geometry you have have selected based on a text or graphical search run earlier...

Sorry for the delayed response Robert (I was out on vacation) and thank you for your reply. Maybe this will clarify. I see where I can show a buffer distance of a selected feature. Is there a way for this buffer to "grab" the polygons the buffer touches and add them to the results window? I can manually trace a polygon and essentially do the operation that way but I was hoping to simplify the process for the end user with only a couple clicks at most.

Again, sorry for the late response and thank you again for your help!

RobertScheitlin__GISP

Chad,

Hmm... What I am understanding you to be asking is very possible using the SPATIAL search portion of the widget, or maybe I am just not understanding you.

When you use the graphical or text search to select your original polygon then you switch to the Spatial search portion and specify a buffer distance and search layer and the polygons (assuming that is the search layer you choose) that intersect the buffer get selected and added to the results. Based on this explanation am I still missing your question?

ChadHall

You have it correct. I wasn't using your widget correctly! I saw the buttons for entirely contained or intersect or envelope and didn't realize you could click that to select the buffer graphic features. Sorry for that; I should've at least attempted to do that before garnering your attentions.

Any idea about the parent/child box checking comment from earlier?

Thank for you putting up with me!!

ChadHall

Call me needy but I've been battling this and don't see it. I've read the help file and I'm not finding it there either and I hate to be a bother. The "Owner Name" search is working correctly but the "Property ID" search is not. I thought I've changed it appropriately since it's a numeric field and not a text field but I keep getting an error when I try to process the request. Code's below unless you need more of the block. Good news is the graphical search and buffer issues are gone so I'm almost there.

<expressions>
<expression alias="Owner Name" textsearchlabel="Search Owner Name [ Example: PUBLIC JOHN Q ]:">
<values>
<value prompt="Example: PUBLIC JOHN Q" isvaluerequired="true">upper(file_as_na) LIKE upper('%[value]%')</value>
</values>
</expression>
<expression alias="Property ID" textsearchlabel="Search Property ID [ Example: 52138 ]:">
<values>
<value prompt="Example: 52138" isvaluerequired="true">PROP_ID = '[value]'</value>
</values>
</expression>
</expressions>

gisgeeknorth

Folks,

I'm stumped. I'm using the eSearch Widget to search a layer with a related table (the features are wells, the related records samples). The relationship class works fine - in the info PopUp the related records appear.

The eSearch Widget works for searching the features, but as soon as I click on the icon to show related records, I get odd behaviour.

- If the floating Data Grid is used, the mouse cursor turns into the "clock" and nothing happens.
- If the Fixed data great is used, then the "Related Results" tab shows up, but it's blank (no data, no rows, no columns). And, I also get the "clock cursor".

The REST endpoint of my service is...
http://54.235.15.249/arcgis/rest/services/MoE/MoEOperationalSDE/MapServer/9

There is indeed a relationship on that layer (ID:1).

Pertinant part of the widget configuration is...
<relates>
<relate id="1" label="Related PGMN Samples 2010" enableexport="true"
      icon="widgets/FortyThree/Search/assets/images/i_relate.png"
      enableprintgrid="true" printitle="Related PGMN Samples 2010">
<fields all="true"/>
   <zoomscale usegeometry="true" zoompercent="1.6" />
</relate>
</relates>

I've added the fixed DG MXML module to the project (I'm using the source).

Thoughts?
Chris

gisgeeknorth

Call me needy but I've been battling this and don't see it. I've read the help file and I'm not finding it there either and I hate to be a bother. The "Owner Name" search is working correctly but the "Property ID" search is not. I thought I've changed it appropriately since it's a numeric field and not a text field but I keep getting an error when I try to process the request. Code's below unless you need more of the block. Good news is the graphical search and buffer issues are gone so I'm almost there.

<expressions>
<expression alias="Owner Name" textsearchlabel="Search Owner Name [ Example: PUBLIC JOHN Q ]:">
<values>
<value prompt="Example: PUBLIC JOHN Q" isvaluerequired="true">upper(file_as_na) LIKE upper('%[value]%')</value>
</values>
</expression>
<expression alias="Property ID" textsearchlabel="Search Property ID [ Example: 52138 ]:">
<values>
<value prompt="Example: 52138" isvaluerequired="true">PROP_ID = '[value]'</value>
</values>
</expression>
</expressions>

Question - what is the data type of your PROP_ID field? You have single quotes around [value] which implies a string. If a string, then you should use the "upper" and "like" syntax as with owner name search.

If the PROP_ID is a number, then I think you have to get rid of the quotes.

KenCarrier

Robert,

Sorry to bother you but I am stuck with some of the new syntax.

I have tried finding in your documentation where I am going wrong but I cannot for the life of me find what I am doing wrong.

I am using ArcGIS Viewer for Flex - Application Builder version 3.4 with your widget.

What I am attempting to do is have a dropdown for PROPTYPE which is a subtype(Short Integer), then a drop down underneath that for ACREAGEDOM which is a domain(Short Integer).

I have tried getting it to work with only ACREAGEDOM but I cannot get the values to populate in a drop down. Although i have got it to work with the subtype field PROPTYPE.

Would you mind looking at my xml and telling me if I am doing something wrong. The rest endpoint is here

Code:

    <layers>
        <layer>
            <token/>
            <useproxy>false</useproxy>
            <definitionexpression/>
            <enableexport>true</enableexport>
            <name>Available Land</name>
            <url>http://maps.monroeohio.org/arcgis/rest/services/WMAS/AvailableLand/MapServer/0</url&gt;
            <expressions>
                <expression alias="Agricultural" textsearchlabel="Search by Property Size...">
                    <values>
                        <value prompt="Select size:" field="ACREAGEDOM" usedomain="true">ACREAGEDOM = [value]</value>
                    </values>
                </expression>
                <expression alias="Residential" textsearchlabel="Search by Property Size...">
                    <values>
                        <value prompt="Select size:" field="ACREAGEDOM" usedomain="true">ACREAGEDOM = [value]</value>
                    </values>
                </expression>
            </expressions>
            <titlefield>PARID</titlefield>
            <fields all="false">
                <field name="BCOMPANY" alias="Contact Company" gridfield="true"/>
                <field name="BNAME" alias="Contact Name" gridfield="true"/>
                <field name="BPHONE" alias="Contact Phone" gridfield="true"/>
                <field name="BFAX" alias="Contact Fax" gridfield="true"/>
                <field name="BEMAIL" alias="Contact Email" gridfield="true"/>
                <field name="PROPNAME" alias="Property Name" gridfield="true"/>
                <field name="ZONE" alias="Zone" gridfield="true"/>
                <field name="ACRES" alias="Acres" gridfield="true"/>
                <field name="PARID" alias="ParID" gridfield="true"/>
                <field name="OWNER" alias="Owner" gridfield="true"/>
                <field name="COMMENTS" alias="Comments" gridfield="true"/>
                <field name="PROPTYPE" alias="Property Type" gridfield="true"/>
                <field name="ADDRESS" alias="Address " gridfield="true"/>
                <field name="HYPERLINK" alias="Brochure Link" gridfield="false" hyperlinkgridfield="true" hyperlinkaliastext="Get More Info"/>
                <field name="AUDHYPLNK" alias="Auditor Link" gridfield="false" hyperlinkgridfield="true" hyperlinkaliastext="Get More Info"/>
                <field name="LATITUDE" alias="Latitude" gridfield="true"/>
                <field name="LONGITUDE" alias="Longitude " gridfield="true"/>
            </fields>
        </layer>
    </layers>

Legacy Code from previous version:

<layer>
  <definitionexpression></definitionexpression>
  <enableexport>true</enableexport>
  <name>Available Land</name>
  <url>http://gis.monroeohio.org/MONGIS/rest/services/AvailableLand/MapServer/0</url&gt;
  <expressions>
   <expression alias="Agricultural" textsearchlabel="Search by Property Size..." field="ACREAGEDOM" usedomain="true" fromsubtype="true">PROPTYPE = 0 AND ACREAGEDOM = [value]</expression>
   <expression alias="Residential" textsearchlabel="Search by Property Size..." field="ACREAGEDOM" usedomain="true" fromsubtype="true">PROPTYPE = 1 AND ACREAGEDOM = [value]</expression>
   <expression alias="Commercial" textsearchlabel="Search by Property Size..." field="ACREAGEDOM" usedomain="true" fromsubtype="true">PROPTYPE = 2 AND ACREAGEDOM = [value]</expression>
   <expression alias="Light Industrial" textsearchlabel="Search by Property Size..." field="ACREAGEDOM" usedomain="true" fromsubtype="true">PROPTYPE = 3 AND ACREAGEDOM = [value]</expression>  
   <expression alias="Heavy Industrial" textsearchlabel="Search by Property Size..." field="ACREAGEDOM" usedomain="true" fromsubtype="true">PROPTYPE = 4 AND ACREAGEDOM = [value]</expression>
  </expressions>
  <graphicalsearchlabel>Use one of the graphical search tools to select Available Land</graphicalsearchlabel>
  <spatialsearchlayer>true</spatialsearchlayer>
  <titlefield>PARID</titlefield>
  <fields all="false">
    <field name="BCOMPANY" alias="Contact Company" gridfield="true"/>
    <field name="BNAME" alias="Contact Name" gridfield="true"/>
    <field name="BPHONE" alias="Contact Phone" gridfield="true"/>
    <field name="BFAX" alias="Contact Fax" gridfield="true"/>
    <field name="BEMAIL" alias="Contact Email" gridfield="true"/>
    <field name="PROPNAME" alias="Property Name" gridfield="true"/>
    <field name="ZONE" alias="Zone" gridfield="true"/>
    <field name="ACRES" alias="Acres" gridfield="true"/>
    <field name="PARID" alias="ParID" gridfield="true"/>
    <field name="OWNER" alias="Owner" gridfield="true"/>
    <field name="COMMENTS" alias="Comments" gridfield="true"/>
    <field name="PROPTYPE" alias="Property Type" gridfield="true"/>
    <field name="ADDRESS" alias="Address "gridfield="true"/>
    <field name="HYPERLINK" alias="Brochure Link" gridfield="false" hyperlinkgridfield="true" hyperlinkaliastext="Get More Info"/>
    <field name="AUDHYPLNK" alias="Auditor Link" gridfield="false" hyperlinkgridfield="true" hyperlinkaliastext="Get More Info"/>
    <field name="LATITUDE" alias="Latitude" gridfield="true"/>
    <field name="LONGITUDE" alias="Longitude "gridfield="true"/>
     
  </fields>
  <links>

   <link includeinresults="false" field="AUDHYPLNK" alias="Auditor Link: Get More Info">
    <linkprefix></linkprefix>
    <linksuffix></linksuffix>
    <iconfield></iconfield>
    <iconprefix></iconprefix>
    <iconsuffix></iconsuffix>
   </link>
   
   <link includeinresults="false" field="HYPERLINK" alias="Brochure Link: Get More Info">
    <linkprefix></linkprefix>
    <linksuffix></linksuffix>
    <iconfield></iconfield>
    <iconprefix></iconprefix>
    <iconsuffix></iconsuffix>
   </link>
   
  </links>
  <icon isfield="false"></icon>
  <zoomscale usegeometry="true"/>
  <autoopendatagrid>true</autoopendatagrid>
 </layer>

JayGeisen

Thanks, Robert! So, why does it work when you add this in the compiled code then?

RobertScheitlin__GISP

Jay,

I thought you said it was not working period since your upgrade of ArcGIS Server?..

RobertScheitlin__GISP

Justin,

I email Bjorn to check the status, but I belive that it is going to be a ArcGIS Server issue and not an API issue.

RobertScheitlin__GISP

Chad,

When you query numbers you do not use the single qoutes.

<value prompt="Example: 52138" isvaluerequired="true">PROP_ID = [value]</value>

RobertScheitlin__GISP

Chris,

There is a bug in the code. As a work around for now just list your relates field and DO NOT use

<fields all="true" />

This will be fixed in the 3.5 release

ChadHall

Chad,

When you query numbers you do not use the single qoutes.
<value prompt="Example: 52138" isvaluerequired="true">PROP_ID = [value]</value>

Thanks again, Robert!

RobertScheitlin__GISP

Ken,

I have nothing in place for using a domain on a field that is not associated with that field in the REST endpoint. What I mean by that is that if you want a dropdown for ACREAGEDOM to come from the ACREAGEDOM domain then the domain has to be listed as a domain of that field in the REST Service endpoint. For example:

ROW_Type  ( type: esriFieldTypeSmallInteger , alias: ROW Type , Coded Values:  [1: Prescriptive] , [2: Deeded] )

KenCarrier

Robert,

Thank you that is exactly what I needed which is a second set of eyes.

The domains are associated at the subtypes level not at the field level. In addition, for some reason when I replicated from SDE to a file gdb the domain did not come over, that was the big issue.

I now have the subtypes and field associated with the domain so I think this will work now.

As always thank you for your help and contributions to the community, it is greatly appreciated!

JayGeisen

Robert,

Right. It stopped working when I upgraded to 10.2. The changes you specified to the eSearch.mxml fixed the issue, however. I'm just wondering why it works when you code it into the mxml, but not in the xml?

RobertScheitlin__GISP

Jay,

As i mentioned earlier I am not sure what might have changed in 10.2 Server.

Patrick Huls

Thanks Robert. Do you plan on recompiling for Flex 3.5? It would be greatly appreciated.

RobertScheitlin__GISP

All,

Version 3.5 of my widgets are in the works. I am just extremely busy right now and will be delayed in getting them out.

ZhujingXia

How to make the intersect result from buffer not zoom to the intersect result.

I am using the Enhanced widget flex 3.0, after I created a buffer around a parcel, I need to choose a criteria layer to see how many criteria intersect with the buffer. Is that possible not zoom to the criteria result, let the map stay with parcel zoom in scale?
The issue is that my criteria layer is extreamly long polygons, after zoom to the result of the criteria, the map is away from the original parcel. That is not what user want.

Could you help me on this ?

Thanks
Zhujing

RobertScheitlin__GISP

Zhujing,

I think what you are looking for is autozoomtoresults="false" in the eSearchWidget.xml

HiranDias

Robert,

Thanks for this wonderful Widget but i have a question, can i search using the BETWEEN command in SQL ? For example: Could i make 2 combos and put their values on a Value tag ? Like this:

<value prompt="pH Min" isvaluerequired="false" userlist="1, 2, 3" prompt="pH Max" userlist="5, 6, 7">pH between '[value]' and '[value]'</value>

RobertScheitlin__GISP

Hiran,

Sure it would look like this though:

                <expression alias="Replacement Score Between" textsearchlabel="Search Replacement Score Between:">
                    <values>
                        <value prompt="Example: 60" autosubmit="false">REPLSCORE BETWEEN [value]</value>
                        <value prompt="Example: 80" autosubmit="false" operator="AND">[value]</value>
                    </values>
                </expression>

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.