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

Nathan,

Are you wanting to specify your own list of values in the xml file?.. Because right now you can use a field that has a coded value domain and it will add a combobox with the domains values if you specify usedomain="true". If you are wanting to manually add values than I will add that to the requested enhancements list but don't see this happening very soon (just to busy).

deleted-user-RjoC4IOGTpoH

Good afternoon Robert.

I hope you are doing well.

Just a request for a future enhancement to the widget. I believe I may have asked this before.

Would it be possible to add the option for the sum of select columns to be displayed in the floating datagrid at the bottom by including the field names in the xml file?

Currently the users have to export each time to calculate them.
Something to consider for a future enhacement if possible.

Thanks again ...

Nestor.

RobertScheitlin__GISP

Nestor,

Version 2.2.9 how has this ability.

deleted-user-RjoC4IOGTpoH

Nestor,

Version 2.2.9 how has this ability.

Fantastic Robert !!

You just made a lot of users happy including me.

Thank You very much.

Nestor.

MarcWeinshenker1

Nestor,

Version 2.2.9 how has this ability.

Robert,

The sum function seems to have been put in for text queries but not for graphical queries. I see sum data accounted for in the function queryFeaturesText but not in the function queryFeaturesGraphical. Is there a problem which prohibits summing the results of a graphical query? I'd like to be able to graphically choose a number of parcels and then sum the area, for instance.

Thanks,
Marc

RobertScheitlin__GISP

Marc,

Hmm... On my live test site it does sum a graphical search if you have more than one record selected using the graphical search.

EDIT:
Well I now see the issue. If you don't do a text search first that shows the sum box than it will not appear in the graphical...

I'm on it...

MarcWeinshenker1

Marc,

Hmm... On my live test site it does sum a graphical search if you have more than one record selected using the graphical search.

EDIT:
Well I now see the issue. If you don't do a text search first that shows the sum box than it will not appear in the graphical...

I'm on it...

Robert,

I wasn't using the text search at all, and now that I try doing that first I am seeing the graphical total. Thanks for figuring it out.

Marc

RobertScheitlin__GISP

All,

Version 2.2.10 is now available. This version has a minor fix and a new document that describes all the needed code changes to make this widget run a search from the URL.

Maybe the last version until 2.2.3 as I am Beta testing the 2.3 FlexViewer right now.

WillHughes1

Robert,

I was successful adding a 2-variable search capability to the default Search widget, and now I am trying to do the same thing for the eSearch widget. I added a cbo box to the widget which is used as a picklist to choose the 2nd search variable (values are hard coded in the SearchWidget.mxml code).
The fault error is: fault code 400, unable to perform query, check your parameters.
Do you see anything I am doing wrong in the code below?
Thanks.
Awesome widget by the way.

Will

SearchWidget.xml (code piece)
<layer>
   <enableexport>true</enableexport>
            <name>Facilities</name>
            <url>http://mywebserver/rest/services/myservicename/MapServer/1</url>
            <expressions>
             <expression alias="Facility Number" textsearchlabel="FACIL_ID [ Example: 1600 ]:">upper(FACIL_ID) = upper('[value]') AND upper(I_ID) = upper('[value2]')</expression>
             
             
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Zoning</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>FACILID</titlefield>
            <linkfield linkprefix="" linksuffix=""></linkfield>
   <icon isfield="true" iconprefix="" iconsuffix=""></icon>
            <fields all="false">
                <field name="FACILID" alias="Facility Id"/>
                <field name="SNAME" alias="Facility Name"/>
                
            </fields>
        </layer>

SearchWidget.mxml (code piece)
if (configSearchText.useproxy && configData.proxyUrl)
     {
      queryTask.proxyURL = configData.proxyUrl;
     }
     var query:Query = new Query();
     var myPattern:RegExp = /\[value\]/g;
     var myPattern2:RegExp = /\[value2\]/g; //added by W.Hughes - variable for installation code
     var expr:String;
     var exprFinal:String = expr; //added by W.Hughes to add second variable to expression
     if (txtSearch.visible){
      expr = queryExpr.replace(myPattern, txtSearch.text);
      expr = expr.replace(myPattern2, cbo2.text); //variable for installation code
     }else{
      expr = queryExpr.replace(myPattern, cbSearch.selectedItem.value);
     }
     //query.where = expr; this is the original code
     query.where = exprFinal //added by W.Hughes

and...........

<s:TextInput id="txtSearch" width="90%" enter="queryFeaturesText()"/>
   <mx:ComboBox id="cbo2" width="40%">
    <mx:dataProvider>
     <fx:Array>
      <fx:String>abcd</fx:String>
      <fx:String>efgh</fx:String>
      <fx:String>ijkl</fx:String>
      <fx:String>mnop</fx:String>
      <fx:String>qrst</fx:String>
     </fx:Array>
    </mx:dataProvider>
   </mx:ComboBox>
   <mx:ComboBox id="cbSearch" creationComplete="{cbSearch.width = wTemplate.width - 40; fnInit();}"
       change="queryFeaturesText()" visible="false" includeInLayout="false"
       labelField="label"/>

RobertScheitlin__GISP

Will,

You have some issues in your code:

SearchWidget.mxml (code piece)
if (configSearchText.useproxy && configData.proxyUrl)
{
queryTask.proxyURL = configData.proxyUrl;
}
var query:Query = new Query();
var myPattern:RegExp = /\[value\]/g;
var myPattern2:RegExp = /\[value2\]/g; //added by W.Hughes - variable for installation code
var expr:String;
var exprFinal:String = expr; //added by W.Hughes to add second variable to expression
//You set this here to equal expr, but expr has not been edited by the replace functions yet.
if (txtSearch.visible){
expr = queryExpr.replace(myPattern, txtSearch.text);
expr = expr.replace(myPattern2, cbo2.text); //variable for installation code
}else{
expr = queryExpr.replace(myPattern, cbSearch.selectedItem.value);
}
//query.where = expr; this is the original code
query.where = exprFinal //added by W.Hughes

MicahVan_Maanen

Robert,
Thank you for the excellent widget.

I do have one question, is it possible to change the Search List Combo box to Radio Buttons? I noticed this on the Parcel Search box on your site and it looks very nice.

RobertScheitlin__GISP

Micah,

If you are willing to modify the source code than yes. When I make changes to widgets I have to think about the thousands of people that have downloaded this widget and if I can make a change work for every one. changing from a combobox to a radio button group will only work in limited situations because of limited widget real estate, It would not look good at all to have 6 radio buttons but 6 items in a combobox is OK.

MicahVan_Maanen

Robert,
Thanks for the reply, that makes perfect sense.

I'll work on modifying the source code.

Sung-JunKim

Robert and All,
This is a great tool and I am using it nicely. I would like to see if there is a way to add AND or OR clause to the existing query. What I like to do is that I would like to search based on multiple columns or a range within a column without adding another combo box. For example,
Example 1: ColumnA = '[value]' AND ColumnB = '[value]'
Example 2: ColumA >'[value]' AND ColumnA <'[value]'

Thanks,
Sung-Jun

RobertScheitlin__GISP

Sung-Jun,

See this post:

http://forums.arcgis.com/threads/15783-Enhanced-Search-Widget-for-FlexViewer-2.1?p=76466&viewfull=1#post76466

MarcWeinshenker1

Hi Robert,

I'm making great headway configuring the eSearch widget for a very specific application. Many thanks for the functionality and flexibility.

I did notice a little quirk, though, and didn't see anything mentioned in this thread as I looked back over a few pages. If I do this:

1) graphically select a parcel
2) buffer on the selected parcel
3) select parcels with the buffer

Then when I minimize the eSearch widget window (only minimize, not close) the selection disappears while the buffer remains in the display. When I restore the widget window to full size the selection comes back. Don't know if this is a bug or a feature, but I think it would be better if nothing disappeared from the display when the widget is minimized, but only when it is closed.

Thanks,
Marc

MattShetzer

Robert,
I'm hoping you might be able to help me on this. I'm using your excellent eSearch 2.2.9 widget. I've got many searches working, but this one is giving me a

"[RPC fault faultstring="Unable to complete operation." faultcode="400" faultdetail="unable to complete Query operation."]" error.

I've got to be missing something.... I'm stuck !!!!

<layers>
<layer>
            <name>Well</name>
            <enableexport>true</enableexport>
            <url>http://server.petro-fs.com:8887/ArcGIS/rest/services/OrrEnergy/OrrEnergy/MapServer/12</url>
            <expressions>
     <expression alias="Well Name" textsearchlabel="Search by Well Name (Wildcards) [Example: Lakes]">upper(F_Name) LIKE upper('[value]%')</expression>
     <expression alias="API" textsearchlabel="Search by API [Example: 05-123-25689 ]">upper(API) = upper('[value]')</expression>
   </expressions>
   <graphicalsearchlabel>Use one of the graphical search tools to select Well</graphicalsearchlabel>
            <spatialsearchlabel>Select the two layers for spatial query</spatialsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <spatialrelationlayer>true</spatialrelationlayer>
   <titlefield>F_Name</titlefield>
            <linkfield linkprefix="">PhotoQuad</linkfield>
            <icon isfield="true" iconprefix="" iconsuffix=""></icon>
            <fields all="false">
                <field name="F_Name" alias="Well" gridfield="true"/>
                <field name="F_Status" alias="Status" gridfield="true"/>
                <field name="API" alias="API" gridfield="true"/>
                <field name="PhotoQuad" hyperlinkgridfield="true" hyperlinkaliastext="Photo Lookup"/>
            </fields>
               <zoomscale>100000</zoomscale>
        </layer>

Thanks again for all your support and excellent tools !!!
Matt Shetzer

RobertScheitlin__GISP

Matt,

Your mapservice must be coming from something other than SDE so you have to change your SQL statement.

F_Name LIKE  '[value]*'

CoryHines

Just curious if anyone else has gotten the same errors that I have when adding the new URL search configuration info.

-1120: Access of undefined property BaseWidget. > error from WidgetManager.mxml
-1120: Access of undefined property _configData. > error from ViewerContainer.mxml

Changed a few things on the lines that each of these is coming up, and added some other statements, but haven't been able to completely get rid of these.

Cory

RobertScheitlin__GISP

Cory,

I will be updating the pdf soon for these oversights:

WidgetManager.mxml add

import com.esri.viewer.BaseWidget;

ViewerContainer.mxml add:

public var _configData:ConfigData;

//Change this line of the postConfigHandler function.
var configData:ConfigData = event.data as ConfigData;
//to
var configData:ConfigData = _configData = event.data as ConfigData;

CoryHines

Thanks Robert!

I also ended up having to change 2 lines in the widgetmanager.mxml's getWidget function

from
widget.setState(BaseWidget.WIDGET_OPENED);
to
widget.setState(WidgetStates.WIDGET_OPENED);

It was still throwing a error for using a reference to a Class.

So far this seems to be working.

I hope you are enjoying the DevSummit.

MattShetzer

That did the trick !!! Thanks Robert.

Matt,

Your mapservice must be coming from something other than SDE so you have to change your SQL statement.
F_Name LIKE  '[value]*'

RobertScheitlin__GISP

Mike,

If you are using the default geometry service that I had in the SearchWidget.xml that goes to esri, than you probably want to point that to your own geometry service instead. If you don't have one yep then just publish one using ArcGIS Server Manager.

JohnBuzzard

Robert,
I was also able to get your url query solution to work with the fixes you listed above, but I am now coming across another little bug. When I do a url search that returns multiple results and hit the "show results in grid" button, the grid view opens up blank with an error back on the widget saying error #1009. Now this only happen when doing a url search. The grid view works fine when searching manually. Any ideas?

screenshot.JPG

RobertScheitlin__GISP

John,

Fix will be out for this today as soon as I compile both versions. Thanks for catching this.

RobertScheitlin__GISP

All,

Version 2.2.11 is now available.

Version 2.2.11 - 03/15/2011
* Fixed showing the datagrid after performing a search from the FlexViewers URL
!!!!!!Requires Mods to several FlexViewer components, See additional instructions!!!!!!
* Enhanced Search Widget URL Search Configuration.pdf has been update for some oversights and omissions.

AlexSanders

Robert,

Is there any way of hiding the url address in the bottom of the pop up info box and replacing it with a linkfieldalias like

<linkfield linkprefix="http://someWebSite/aspx/web/details.aspx?p_entity=" linksuffix="" linkfieldalias="Click Here for More Information">parcels2.OVER_COND</linkfield>

Alex Sanders
GIS Analyst
Texas General Land Office

RobertScheitlin__GISP

Alex,

Not currently, The info popup window is not specific to the Enhanced Search widget (it belongs to the viewer in general) and there for is not customized by my widget.

AlexSanders

Thanks for the response and the great widget.

Alex Sanders

AlexSanders

One more thing. I changed the font size and style in the defaults.css file for the .WidgetTitle so that the Widget headings would be larger and easier to read. I noticed that your eSearch and Identify widgets did not change the title size. Do you have them configured to not react to that .css file?

Alex Sanders

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.