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.

Vind meer berichten getagd met

Accepted answers

All comments

JulieWilliams1

All,

New Version now available:

Version 3.5.3 - 10/22/2013
* Fixed issue With preload="minimized" and the dropdownlists.
* Fixed issue with SubTypes and Domains assigned to subtypes.
* Fixed issue with text qualify userlists and the 'all' option.

Thanks, so much, Robert! I really appreciate you taking the time to look at the domain issue! We really, really love this tool and use it a lot in our maps. I'll give the new version a try - thanks, again!

Julie Williams

MatthewColwin

Robert -

I'm attempting to utilize the Enhanced Search Widget to meet a requirement for a class I'm in. I've published a map service with a points layer ("gamefish sites") that contains a number of different fields, the two of importance being gamefish_commonname (fish name) and gamefish_weight (average fish weight in grams). We are asked to allow the user to query for a user defined gamefish and the weight of that species greater than a user specified input.

Therefore, what I hoped to do was to alter the configuration file of the Enhanced Search Widget so that two options would be available to the user. First, they would be prompted to choose a fish name from a dropdown, and second, they would enter a number (weight), and then hit "search" to find gamefish sites that meet both requirements. In my code below (I've only posted the part I've edited), I was able to successfully get both of the dialogs (fish dropdown and weight numeric entry box) to appear, and I made it so the fish type was required but weight was not. If no weight is entered, the search works correctly. However, if a weight is entered, I get this error:

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

My current configuration file has two different views so the user can see these two search criteria. I'm very new to HTML and am unsure how to make it so the user MUST enter a fish type, and CAN enter a weight (if necessary, I can make the weight required as well) in order to get the proper results.

Any help you can provide would be GREATLY appreciated.

<configuration>
    <layers>
        <layer>
            <token/>
            <definitionexpression/>
            <enableexport>false</enableexport>
            <name>Gamefish Sites</name>
            <url>http://152.1.13.55/arcgis/rest/services/GEWA/GEWA_FishSamplingSites_Assignment19/MapServer/0</url>
            <expressions>
                <expression alias="Gamefish Search" textsearchlabel="Search by Common Name (and optionally also by average weight in grams):" isvaluerequired="true">
                    <values>
                        <value prompt="Example: Bluegill" uniquevalsfromfield="gamefish_commonname" isvaluerequired="true" autosubmit="false" operator="AND">gamefish_commonname = '[value]'</value>
      <value prompt="Example: 20" isvaluerequired="false" autosubmit="false" >gamefish_weight > '[value]</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Gamefish Sites</graphicalsearchlabel>
            <spatialsearchlayer>false</spatialsearchlayer>
            <titlefield>Gamefish_Site</titlefield>
            <fields all="false">
    <field name="siteid" alias="Site ID" visible="true" sort="asc|1|string"/>
    <field name="description" alias="Site Description"/>
    <field name="x_coord" alias="X-Coordinate"/>
    <field name="y_coord" alias="Y-Coordinate"/>
    <field name="gamefish_sitevisitid" alias="Site Visit ID"/>
    <field name="gamefish_commonname" alias="Common Name"/>
    <field name="gamefish_latinname" alias="Latin Name"/>
    <field name="gamefish_monthvisited" alias="Month Visited"/>
    <field name="gamefish_yearvisited" alias="Year Visited"/>
    <field name="gamefish_datasheet" alias="Data Sheet"/>
    <field name="gamefish_weight" alias="Average Weight"/>
   </fields>
            <links/>
            <zoomscale usegeometry="true" zoompercent="1.2"/>
            <autoopendatagrid>false</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates/>
            <symbology>
                <picturemarkersymbol url="assets/images/i_target.png" height="15" width="15" xoffset="0" yoffset="0"/>
            </symbology>
        </layer>
    </layers>

DongxingMa

Dongxing,

Is it possible for you to provide a sample of your data in a File GDB for testing?

Thank you, Robert! I have uploaded our sample data, it's OtaySewertest.gdb.zip.

The widget layer box width issue is not a problem anymore, and the widget works for subtypes field and domain now, but--it's only when without joined tables associate with the layer! The new problem is like: if the layer has a joined table with it (the fields in my map service is like:

-----------------------------------------------------------------------------------------------------
ssGravityMain.OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )
ssGravityMain.Subtype ( type: esriFieldTypeInteger , alias: Subtype )
ssGravityMain.FacilityID ( type: esriFieldTypeString , alias: FacilityID , length: 30 )
......
otaypub.dbo.vw_wASBUILTS_URL.SID ( type: esriFieldTypeInteger , alias: SID )
otaypub.dbo.vw_wASBUILTS_URL.AsBuiltNo ( type: esriFieldTypeString , alias: AsBuiltNo , length: 50 )
otaypub.dbo.vw_wASBUILTS_URL.ASBUILTURL ( type: esriFieldTypeString , alias: ASBUILTURL , length: 87 )

-----------------------------------------------------------------------------------------------------

then it can't search the layer anymore, even when the subtype field turned off (before it worked when subtype field turned off). The error is still the "400" error, same as before.

Here I attached our sample sewer datasets, please test the three layers and join the table: asbuiltTab to the layers by "asbuiltno" fields.

I really want to use the wonderful widget in our flex viewer, hope it won't cost you too much time to make it works for both subtype field (with domain), and the joined table and its fields. Please let me know if you need anything else for testing.

Really appreciate your help!

Dongxing

OtaySewerTest.gdb.zip

RobertScheitlin__GISP

Matthew,

So your issue is in your second expression value:

<value prompt="Example: 20" isvaluerequired="false" autosubmit="false" >gamefish_weight > '[value]</value>

To start you have a single qoute in front of the [value] (unbalanced). The second part of your issue is that when searching numeric field you don use single qoutes as this indicates a string and not a number. Third is you should escape < and > values in XML with < and >

Correct value:

<value prompt="Example: 20" isvaluerequired="false" autosubmit="false" >gamefish_weight &gt; [value]</value>

RobertScheitlin__GISP

Dongxing,

Thanks for the sample data. I will see what I can come up with.

MatthewColwin

Robert -

Thank you so much for your extremely fast response! Your fixes worked like a charm! I'm in a distance program so I don't really have anyone to check my code for simple syntax errors (the single quote), let alone to help me with anything more complex. I really appreciate it! For the record though, I did have the proper greater than notation in there initially, but wondered if that was causing my issue. I'm glad to have you confirm I was on the right track there.

Thanks again! Getting this solved will allow me to sleep much better tonight.

-Matt

JulieWilliams1

All,

New Version now available:

Version 3.5.3 - 10/22/2013
* Fixed issue With preload="minimized" and the dropdownlists.
* Fixed issue with SubTypes and Domains assigned to subtypes.
* Fixed issue with text qualify userlists and the 'all' option.

Hi Robert!

Just wanted to let you know I downloaded the latest version of the tool and it works beautifully! Fixed my domain problems, which will make my users very happy! Thanks, so much, for your help with this and for getting it working for me - it's an awesome tool!

Julie Williams

RobertScheitlin__GISP

Julie,

Good to hear. Thanks for your willingness to provide the data which helped me resolve this issue.

RobertScheitlin__GISP

Dongxing,

Well I have some bad news. It turns out that this is a documented ArcGIS Server issue. There was a bug logged NIM083086 and the Bug was rejected by the server development team "Known Limitation On Server End". The other user that had this same situation was told to remove the join or the Subtype field (not much of a resolution). I have added my name to the nimbus bug for this issue to see if it can be reopened and possibly get fixed without out a lame response from the development team, to just remove the join or the subtype field. I would recommend that you report the bug as well (make sure that you duplicate the issue using the OTB Search widget and not the eSearch, or they will just blame it on the custom widget).

DongxingMa

Dongxing,

Well I have some bad news. It turns out that this is a documented ArcGIS Server issue. There was a bug logged NIM083086 and the Bug was rejected by the server development team "Known Limitation On Server End". The other user that had this same situation was told to remove the join or the Subtype field (not much of a resolution). I have added my name to the nimbus bug for this issue to see if it can be reopened and possibly get fixed without out a lame response from the development team, to just remove the join or the subtype field. I would recommend that you report the bug as well (make sure that you duplicate the issue using the OTB Search widget and not the eSearch, or they will just blame it on the custom widget).

This is really too bad! I have spent quite a lot of time trying to make it work, didn't find the bug info until you told me. Now I understand why even you couldn't make it work. I definitely will report the bug to ESRI. I think my case is a very common case, why they don't want to fix the bug?

Come back to the eSearch widget, I think joined table and fields are much more important than subtype field(which I can create a specific version of map services for eSearch to use, in this map service turn subtype field off) for us, so I may have to use the 3.5 version eSearch instead of the latest version 3.5.3.

By the way, is the "OTB Search widget" just ESRI's regular search widget? We have been using it for two years, I knew it only directly displays subtype value as number (code), can't automatically transfer code into description and display it, but it doesn't give a error, doesn't crush the search. So, I created domain tables for all our subtype and domain fields, and related them together, in identify and search widgets configuration files, make them display the description fields while searching by the code fields.

I wonder if you have a similar version of eSearch, that it can handle joined table and fields well, and just treat subtype field as a regular field to read and display the code numbers, but won't give error message, won't crush the search process? If you do have such a version, or you can easily create such a version, that would still be a very good news for users like me (please consider about it if it won't cost you too much time). Anyway, we need push ESRI develop team to fix their bug!

Thank you very much for your information, your widgets and all the work you are sharing with the community!

Dongxing

bxo2pgegispotal

Robert,
I've been using the tool with great success for a few years now and thanks! I have a question on the amount of records that can be returned via a graphical search or text search. Is there a limit on the application end to how many records can be retrieved and exported via the tool? I know about the setting on the AGS Server side, but when I select a large amount of records from a layer (say gt 50,000) using the graphical search it will select the features, but the search results container will be empty and I cannot export the table out to csv. Is this a limitation or can I change a setting somewhere?

Also I'm on version 3.4

Any help is greatly appreciated.

Thanks,
Brandon

DerekHunter1

I may have missed it in my searches of this thread, but I cannot seem to determine why the Search Layers drop-down in all of the search types in the widget do not show any layers. Its as if they are there but I can't see them.

RobertScheitlin__GISP

Dongxing,

I knew it only directly displays subtype value as number (code), can't automatically transfer code into description and display it, but it doesn't give a error, doesn't crash the search

This is strange as I get error 400 when using the standard esri search widget when using a joined layer that has a subtype. Actually That is the test case I shared with esri when reporting this bug.

Also strange that you say

can't automatically transfer code into description and display it

esris search widget does handle subtype fine as long as there is no join as well.

Whether you leave the Subtype field out of your eSearchWidget.xml field list or not does not matter as esri adds the subtype field automatically in the API when a query is done on a layer that has a subtype defined in its REST end point. The only way to get past that is to hide the Subtype field in the MXD before you publish the map service. Once you hide the SubType field in the MXD and republish the service (with the Join), then version 3.5.3 works just fine as well as older versions of the eSearch.

so I may have to use the 3.5 version eSearch instead of the latest version 3.5.3

Why?.. In 3.5.3 Subtypes works and joined tables has worked way back since the 2.x version of the widget.

RobertScheitlin__GISP

Brandon,

I do not have a hard number to give you. The big thing to remember is that the Viewer is not ArcMap on the Web. The Viewer only have a portion of the memory that is allocated to the browser application (as it is a browser plug in) vs ArcMap is a application and has access to larger amounts of memory. So you might (or might not) be able to do 50,000 points, but 50,000 polygons is not feasible as the eSearch results are added to the map as a FeatureLayer (thus the plugin actually allocated memory for the geometry for each result, which is drawn client side). There is a reason that esri sets the default of a map service to 1000 features.

RobertScheitlin__GISP

Derek,

Hmm... When did this start happening? You either have something really screwed up in your eSearchWidget.xml or you have found a bug no one else has seen. When you say the drop down is empty, is your drop down width extremely small?

DerekHunter1

I didnt think there were major changes to the config structure, so I pretty much used my 3.2 version esearch xml config. I attached the config.

Derek,

Hmm... When did this start happening? You either have something really screwed up in your eSearchWidget.xml or you have found a bug no one else has seen. When you say the drop down is empty, is your drop down width extremely small?

eSearchWidget_Whiting.zip

RobertScheitlin__GISP

Derek,

Which version of the widget are you using? Are you specifying the width and height attributes in the widget tag of the main config.xml for the eSearchWidget?

DerekHunter1

3.5 is the version.   Here is my eSearchWidget portion of the main config.

<widget label="Search" right="15" top="209" preload="open"
                icon="assets/images/i_search.png"
                config="widgets/eSearch/eSearchWidget_Whiting.xml"
                url="widgets/eSearch/eSearchWidget.swf"/>

I apologize as I may not be effectively explaining my issue. The issue I am seeing isn't related to the position of the widget, but rather the size of the drop-down now allowing the layers to be seen. Its confusing as I didn't change the mxml at all, just the eSearchWidget.xml file which I attached in my previous response.

Derek,

Which version of the widget are you using? Are you specifying the width and height attributes in the widget tag of the main config.xml for the eSearchWidget?

RobertScheitlin__GISP

Derek,

Ahh... That was what I was looking for. Just add a width attribute to the eSearch Widget in the main config.xml
This is a new Bug in the 3.5.3 version. It will be addressed in 3.5.4.

<widget label="Search" right="15" top="209" preload="open"
                icon="assets/images/i_search.png" width="400"
                config="widgets/eSearch/eSearchWidget_Whiting.xml"
                url="widgets/eSearch/eSearchWidget.swf"/>

DerekHunter1

Thanks so much!

Derek,

Ahh... That was what I was looking for. Just add a width attribute to the eSearch Widget in the main config.xml
This is a new Bug in the 3.5.3 version. It will be addressed in 3.5.4.
<widget label="Search" right="15" top="209" preload="open"
                icon="assets/images/i_search.png" width="400"
                config="widgets/eSearch/eSearchWidget_Whiting.xml"
                url="widgets/eSearch/eSearchWidget.swf"/>

DongxingMa

Dongxing,

This is strange as I get error 400 when using the standard esri search widget when using a joined layer that has a subtype. Actually That is the test case I shared with esri when reporting this bug.

Also strange that you say esris search widget does handle subtype fine as long as there is no join as well.

Whether you leave the Subtype field out of your eSearchWidget.xml field list or not does not matter as esri adds the subtype field automatically in the API when a query is done on a layer that has a subtype defined in its REST end point. The only way to get past that is to hide the Subtype field in the MXD before you publish the map service. Once you hide the SubType field in the MXD and republish the service (with the Join), then version 3.5.3 works just fine as well as older versions of the eSearch.

Why?.. In 3.5.3 Subtypes works and joined tables has worked way back since the 2.x version of the widget.

Hi Robert,

This is really interesting, we have some different findings and test results:

1>I have been using ESRI's regular search widget, it does handle joined table/fields well, and at the same time, I mean while the joined table exists, it can display and even search by subtype field, won't give error or stop search process, the only issue for me is: it doesn't display subtype's description, it just directly returns the code number. (seems different with your finding!)

2>for your eSearch widget 3.5.3, I found when no joined table exists, it handles subtype field well, returns the description; but if a joined table and a subtype field both exist (change field names in the configuration accordingly, of course), then the esearch process crushes, gives the "400" error. (are you seeing different result when both subtype field and joined table existing in the search layer?)

3>I thought eSearch 3.5.3 cannot handle joined table even subtype field turned off in the mxd, so I said that I may have to go back to use 3.5 version. This is a mistake. I found the subtype field wasn't turned off yesterday when testing.

Now I am sure as long as subtype field turned off, eSearch 3.5.3 handles joined table/fields well, so I will use the latest version eSearch.

4>I still hope you make a version that can have subtype field and joined table/fields co-existing in the search layer, won't give error, can finish search, just treat subtype field as a regular field, directly return the code number. This way, we can use a domain table join to the subtype field, and search by subtype field but return the joined domain table's description field. This is what I have done using the OTB search widget.

Hope I have made my points clearer now. Please advise me if you see any better solution.

Thanks!
Dongxing

RobertScheitlin__GISP

Dongxing,

This might be a difference in ArcGIS Server 10.2 that I am using and 10.1 that you are using. Because using 10.2 and the OTB search 3.5 w/Join and w/Subtype the search fails.

Because of my finding with the 10.2 of server and the fact that I don't have control of the API adding the subtype field if it is present in the Rest Endpoint. I can not make a version that will work as you are wanting.

JayHalligan

I have been using the esearch widget for some time now, but I have just run across a problem and I am not sure what is causing the issue. I have published an X,Y event layer to our server on Amazon EC2 which is dynamically reading a SQL table that is updated nightly. But....When searching the event layer

a)uniquevalsfromfield causes all of the search values to not work
b)without the expression uniquevalsfromfield, the widget is only returning the first value it finds

Any ideas? The widget works fine on our internal server(and internal SQL) but not when I transferred the widget. It also works fine on the server when the database was copied to the amazon.

I figured out that I lost my "Object ID" on the event layer when pointing the source information to a new database. This was causing only the first feature found to be returned. Great Widget so thanks again.

RobertScheitlin__GISP

Jay,

Glad you got it resolved. I hate having to say I could not help in that senario.

KirstenLuzik

Robert,

I cannot seem to figure out how to get the results to appear in a table. The search executes correctly and I can click on the results tab in the search window to see a list of results, but I cannot figure out how to get the results to appear in a separate table. I have checked and double checked my code in both my main config.xml file and my eSearchWidget.xml file. Can you please point me into the right direction?

Thanks,

Kirsten

RobertScheitlin__GISP

Kirsten,

If you look at the example eSearchWidget.xml that comes in the download or read the configuration pdf you will see that for a field to appear in the table you need to define that that field is a gridfield by using the gridfield="true" attribute on a field. If you use the

<fields all="true">

then you do not have this option.

NedCake

Hi Robert,
Hope this message finds you well.

I'm experiencing a problem with eSearch3.5.3 in SFV3.5. The search layer and search field pick list labels are missing. It happens with or without preload. It occurs on both my customized esearch.xml and the OTB esearch.xml. I saw a previous message about this problem being fixed at 3.5.3. I downloaded and tested es3.5.3 from both esri and github. Have I missed something? Appreciate any help.

[ATTACH=CONFIG]28737[/ATTACH]

Much thanks from this SVF junkie for all over your amazing work over the years!
Ned Cake
TLCGIS

esearch.png

RobertScheitlin__GISP

Ned,

Actually the fix for what you are seeing will not be out untill the next release. But there is a simple workaround for this isse in 3.5.3. All you need to do is add a with attribute to the widget tag in the main config:

width="400"

NedCake

Thanks Robert! That did the trick...
Ned

Ned,

Actually the fix for what you are seeing will not be out untill the next release. But there is a simple workaround for this isse in 3.5.3. All you need to do is add a with attribute to the widget tag in the main config:
width="400"

JamesAgidius

Hi There Again. Still Very new to this stuff, so I apologize in advance if my questions have previously been answered else where.

I have recently downloaded the esearch widget (uncompiled) and added it to my project in Adobe Flash Builder 4.7. I am using the api for flex 3.5, flex sdk 4.6, and esearch widget 3.5.3.

I have added the esearch to widgets, added the mxml files to my flex modules list, and added the images to src.assets.images.

I have configured the following bit of the eSearchWidget.xml, defining searches on two different layers of the same mapservice (I
think)
        <layer>
            <token/>
            <definitionexpression></definitionexpression>
            <enableexport>true</enableexport>
            <name>Zoning</name>
            <url>http://*************/rest/services/Planning/MapServer/4</url>
            <expressions>
                <expression alias="Zoning" textsearchlabel="Search by Zoning:" isvaluerequired="true">
                    <values>
                        <value prompt="Example: Rural Residential" userlist="Rural Residential,Commercial,Motor Business,
                        Multiple Family Residential,Municipality,Single-Family Residential,Single-Family Residential (R-1),
                        Suburban Residential" isvaluerequired="true" autosubmit="false" operator="AND">
                        upper(ZONE_TYPE) LIKE upper('%[value]%')</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Zoning</graphicalsearchlabel>
            <spatialsearchlayer>false</spatialsearchlayer>
            <titlefield>ZONING_TYPE</titlefield>
            <fields all="true" />
            <links/>
            <zoomscale usegeometry="true" zoompercent="2"></zoomscale>
            <autoopendatagrid>false</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates/>
            <symbology>
                <simplefillsymbol color="0xff0000" alpha="0.5">
                    <outline color="0xff0000" alpha="0.8" width="2" />
                </simplefillsymbol>
            </symbology>
        </layer>
        <layer>
            <token/>
            <definitionexpression></definitionexpression>
            <enableexport>false</enableexport>
            <enableprintgrid title="Building Permits">true</enableprintgrid>
            <name>Building Permits</name>
            <url>http://***************/rest/services/Planning/MapServer/0</url>
            <expressions>
                <expression alias="Building Permit" textsearchlabel="Search Permits by Permit Number">
                    <values>
                        <value prompt="Example: 2009-053" isvaluerequired="true" autosubmit="false">PERMIT_ = '[value]'</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Building Permits</graphicalsearchlabel>
            <spatialsearchlayer>false</spatialsearchlayer>
            <titlefield>PERMIT_</titlefield>
            <fields all="true" />
            <links/>
            <zoomscale usegeometry="true" zoompercent="2"></zoomscale>
            <autoopendatagrid>false</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <symbology>
                <simplemarkersymbol/>
            </symbology>
        </layer>

The problem that I am having, is that only the first search appears in the eSearch widget when run, and the "layer" button drop down menu on the widget doesn't work. (Clicking on the Layer button produces a vertical line on the widget)

Any ideas on what I may be doing wrong here?

Thanks in advance.

-James

pulldown.jpg

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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