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 II

RobertScheitlin__GISP

All,

I am pleased to announce the next release of my eSearch Widget.

http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

Version 2.5.1.7 - 4/19/2012
* Added ability to search (flat/standalone/no geometry) tables.
* This time all Zooming uses the same scaling (popup, datagrid, widget results, zoom to all).
* Added Relates icon/button to datagrids so that you can click on it in the datagrid to
open relates choice dialog.
* Move all skins to a skins package for cleaner organization.
* Links that are not associated with a field now work.
* Ability to disable the relates tab in the fixed widget is now configurable.

Find more posts tagged with

Accepted answers

All comments

MichelleKinseth

Michelle,

Do you mean that you manually (in the code made the button not visible) or you used the method of setting the multipartgraphicsearch to false in the XML?

I was able to do both, actually, but when I couldn't tell what was affecting the changes I started over with a fresh version of the widget. However, the search button does not go away when I change the <multipartgraphicsearch> tag to false in the XML. At this point I've edited nothing else in the widget other than the XML's. The search does not execute automatically either, so I don't know if I'm missing something obvious.

RobertScheitlin__GISP

Michelle,

The only thing that the multipartgraphicsearch equals false does is sets the eSearch Widgets GUI to not have the "enable multi-part graphics" checked by default. Is that check box checked or not in your GUI? what happens when you physically un-check it and then draw a graphic on the map?

MichelleKinseth

I was able to do both, actually, but when I couldn't tell what was affecting the changes I started over with a fresh version of the widget. However, the search button does not go away when I change the <multipartgraphicsearch> tag to false in the XML. At this point I've edited nothing else in the widget other than the XML's. The search does not execute automatically either, so I don't know if I'm missing something obvious.

Ah, I see. When I physically uncheck the box and draw a geometry the search executes and I get results. I don't know why it's not working in the code. Let me try this once more. Very well could be (likely is) user-error on my part.

MichelleKinseth

As suspected, user-error on my part. There are TWO <multipartgragpicsearch> tags in the XML. missed one of them first time through. Thanks for your help, Robert!

RobertScheitlin__GISP

All,

A new version is now released:

Version 3.0.13 - 10/25/2012
* You can now print from the datagrid (floating or fixed). The Print output is properly paginated
based on the number of columns (and their widths) and the number of rows. The print output has
several configurable option for header colors, footer elements, etc. The print honors any sort
applied to the datagrid.
* Export to csv and text now honors the sort applied to the datagrid.
* Fixed bug with resetting required fields when the search is cleared.

MichelleKinseth

Robert, can you confirm to me that the eSearch URL Search cannot cycle through multiple layers? If I'm understanding your documentation for this feature correctly, it can only perform the URL search on one layer (the top one in the config). Correct?
Thanks, Michelle

RobertScheitlin__GISP

Michelle,

No the top layer in the config file is not the only one that can be searched.

The search will be performed on the first layer and first expression of that layer in your
SearchWidget.xml file by default if you do not specify otherwise.

http://gislap134/FlexViewer3.0/index.html?search=R1&slayer=0&exprnum=0&showdatagrid=true

MichelleKinseth

Michelle,

No the top layer in the config file is not the only one that can be searched.

http://gislap134/FlexViewer3.0/index.html?search=R1&slayer=0&exprnum=0&showdatagrid=true

ah, I misunderstood the text. thanks.

RhettZufelt

Odd behaviour using uniquevalsfromfield tag.

I have noticed that if you use more than one uniquevalsfromfield in an expression, it will only populate ONE of the dropdown boxes. You need to switch to a different search dropdown, then back, and it will populate the "next" dropdown. If you have three, you need to switch from/to the layer three times to get all the dropdowns to populate.

Short term test map here:

http://www.easbio.com/otb/

zoning layer has three uniquevalsfromfield value expressions. Need to switch back and forth to get them all to populate.

R_

also, I see that the "blank" value added to the list when isvaluerequired="false" is only for the userlist. Would be a nice "enhancement" for the uniquvalue list as well.

I added this to the PaginQueryTask.as as it does what I am after. However, this, of course, ALWAYS adds the blank value regardless of isvaluerequired or not.

   //loop over all the properties in the tempPropertyArray
   distinctValuesCollection.addItem({value: " ", label: " "});
   for (var propertyName:String in tempPropertyArray) {

SveinungBertnesRheim_0-1738584096493.png

RobertScheitlin__GISP

Rhett,

These issue are now on the list to be addressed.

BrianKraus

Robert,

I've followed your widgets and work for some time now, but have only just now dived into using them in my application. First off, very excellent work on everything you've done. I realize my answer might be in the forums already, but I thought I would ask first then beg forgiveness/search for it second (I have a few tight time constraints). I may have a few questions, but I'll start easy first.

The functionality you've recently included - the ability to select multiple features prior to executing the search - is very helpful. One of my applications goals is simple: I need to be able to select multiple counties (grabbing their name and FIPS) and send that selection of counties off to a python simulation code I have developed elsewhere. My first question is, how can I keep an initial set of search results that a user might generate, if that user should need to add more selections after the first set is collected? For example: I can select 'graphical search' interface, choose 'point selection', and 'enable multi-part graphics'; then place a few points in county centers, then click the 'search' button. The results are displayed on the map and on the 'results' page of the widget. With the selections still highlighted, I can place some more selection points in new counties. However, if I now go back to the 'graphical search' interface page to re-click the search button, the original selection is cleared and replaced with the new counties I selected. What I am curious to know if the widget can be modified to do is to continuously add my new selections to (what I presume is) the ArrayCollection until at some point I'm done. I plan on letting users choose a state to zoom to and then choose their counties, then allow them to zoom to another state and continue the process until they have the counties they need.

I'll continue reading through the documentation tomorrow as perhaps the answer is in there, but again, I thought I'd toss it out and see if the strength of the forum can help. I'll have a few more questions after this, but I thought I would start slow first. (EDIT: I have looked at the clear() function and notice a lot of things can get erased from in there and don't know if that is the culprit or not)

Thanks and regards,
Brian K.

RobertScheitlin__GISP

Brian,

Currently the eSearch Widget does not support "Add to current selection". It would be possible to add this functionality but my schedule right now is not where I have the time to look into this enough to even give advice on code changes. I can tell you that the Selection Widget from Mark does this already. You could use this or just glean code from his widget.

http://www.arcgis.com/home/item.html?id=20ed6af9ab204548bbf092d51b51fef8

BrianKraus

Thanks Robert.

I had been tooling around with that widget, but apparently had completely missed that 'options' page. I think I might be able to utilize his code merged with some of yours to make things work.

I have a second, naive-like question, that while not directly related to your widget, I hope you or someone can point my in the right direction.

Since your selection method (and original Search widget too) stores selection information into objects stored within an ArrayCollection, my dumb question is - how do I pull information out of that ArrayCollection? I understand it is a container holding multiple objects that have been constructed of the selection information. In my example it would just be the name and FIPS of a county. But for the life of me I'm having the hardest time pulling out that information to create a list of strings ("county1","county2",etc) to use as input for my simulation code. Is this as simple as a for-loop like iteration to go through each object in the collection? I'll repost this question elsewhere too, but I thought I'd start here.

Brian

RobertScheitlin__GISP

Brian,

The searchResultAC var that my widget maintains is an ArrayCollection of SearchResult objects. So each object in the ArrayCollection is a SearchResult object and thus has properties like title, icon, content, zoompercent, zoomscale, point, links, graphic, selected, oid, multi, relateicon, relates, and relatetooltip. So the problem for you is going to be that the field values that you are looking for are likely to be concatenated into one string in the content property. It would be possible to split that string by the string " " and that would get you an array of strings that look like this "County: Calhoun" Than you would have to use flex commands like substring to get just what is between the "" and the "".

RobertScheitlin__GISP

next version 3.0.14 is now available.

Version 3.0.14 - 11/14/2012
* Fixed bug where if more than one uniquevalsfromfield was used in an expression
Only one would populate the dropdown.
* uniquevalsfromfield now are aware of isrequired attribute and add a blank entry
in the drop down if necessary.
* Added delay for mouseover in datagrids to allow user to exit datagrid and choose
a button from the popup
* The popup shown from the search results and datagrid is the same popup that gets
displayed when you click on the search graphic on the map.
* Added the ability to add and remove from current selection as well as create a new
selection (which is the default).
* Fix bug where individual layers symbology specified in the eSearchWidget.xml was
not being used with certain spatial searches.
* Added support for disabling search widget results (just use <disablebuttons>result</disablebuttons>).
* Added support for disabling popups completely for this widget.

AntGiles

Robert,

Am I missing something I can't see any option to add to or remove from selection on your sample,

Regards

Anthony

RhettZufelt

From the sample site:

[ATTACH=CONFIG]19292[/ATTACH]

R_

untitled1.jpg

AntGiles

R_

Thanks for that, for some reason even after I deleted my browser history, closed and re-opened the browser, deleted the flash local storage it still would not show the update.

I had to do a shut down restart of my laptop before the changes came through.

Not experienced that before but all good now

Regards

Anthony

RhettZufelt

Good to hear.

I haven't had to go through the shutdown/reboot computer since I got away from the web.ADF format

)

R_

RobertScheitlin__GISP

All,

I would like to request some feedback.

Are the enhancement I am making going in the right direction?
What do you think about them?
I have been trying to hit some of the BIG most requested features recently but I have not heard back from the community on these.
Is the widget getting to complicated?

RhettZufelt

Have not had a chance to test it out yet, hopfully this week. However, I think the changes you made are great.

Should get a chance to test drive it thoughly soon.

As far as getting to complicated, so far, I'd say no, it's just getting better.

R_

RobertScheitlin__GISP

Rhett,

What about printing the datagrid in the 3.0.13 release? Have you used it?

RhettZufelt

Just tested it to make sure that it worked.

I have passed a "test" map onto some users, am waiting for feedback on it.

Not much feedback yet, but a couple of them noticed that it showed up and really like the capability. Mostly, they were exporting the datagrid, then printing from Excel. this makes it easier for them.

Hope to catch up here this week, and will be able to test it fully before long.

R_

While on enhancement subject, I may have missed it, but an option to determine the export file type allowed would be nice. Some of my users don't understand the problems with exporting to csv format with data that has a lot of commas/delimeters in it (I know we can change the separator). Would be nice to force them to only have text as the export format. Maybe a _enableCSVExport and a _enableTXTExport or something so visibility can be set separately for each? Of course, this is easy for me to just hardcode in the mxml, and not sure how much need there is, but would be nice.

AntGiles

Robert,

I think the additions you are adding are excellent, as for getting to complicated I don't think so. People can choose to make the configuration complex but if they just want a simple search they do not have to make use of all the functionality available.

One enhancement that would be good, not sure how hard it would be to implement though, would be when setting up the expressions having an attribute called fieldType in the value tag that could contain text,number,date,combo and depending on what is set would determine the UI element used in the widget, i.e:

text -- TextInput Control
number - NumericStepper control
date -- DateField control
combo -- ComboBox control

this would force the users to use the right format and hopefully avoid errors

Keep up the good work

Regards

Anthony

RhettZufelt

Hey Robert,

Been playing with the latest version a little and can not get the uniquevalsfromfield expressions to populate with the blank, doesn't matter what isvaluerequired is set to. the userlist it is appending the blank when false but not the uniquevalsfromfield.

Also, curious how one is supposed to make the popup be the same as clicking on the map? I have tried adding the same service I am searching to the map as both type feature and dynamic, setting my desired popup.xml file for each. Have tried combinations of <popupsdisabled>true</popupsdisabled> true/false. Basically, if set to true, I do not get the popup when I click/doubleclick on the data grid or results list but I do get one (actually two) when I click on the selected feature, it will give me the esearch popup as "1 of 2" and it is the popup info as configured in the esearchwidget.xml. The second one is the popup that follows my popupconfig.xml.

So, was wondering how this is supposed to work, and what one needs to do to get it working that way?

Thanks again,

R_

RobertScheitlin__GISP

Rhett,

curious how one is supposed to make the popup be the same as clicking on the map?

I should have explained this one better. My statement

The popup shown from the search results and datagrid is the same popup that gets
displayed when you click on the search graphic on the map.

notice my bolded text, search graphic not a popup.xml that you define in the main config.xml for a layer. As far as the uniquevalsfromfield adding a blank I had this
fixed at one point them made some more code changes to account for a possible empty string value being in the data and I broke it again. But I now have it fixed again. Please re-download the widget.

RhettZufelt

Rhett, I should have explained this one better. My statement notice my bolded text, search graphic not a popup.xml that you define in the main config.xml for a layer.

I see. Guess I thought it was always the same popup when fired anywhere from the eSearchWidget.

As far as the uniquevalsfromfield adding a blank I had this fixed at one point them made some more code changes to account for a possible empty string value being in the data and I broke it again. But I now have it fixed again. Please re-download the widget.

Good to hear this as I was a little concerned that I was doing something wrong as I couldn't repeat the results on your test site, even though it was reporting the same version (thus another unmodified test app). And yes, it appears to be fixed now.

Have noticed an issues still with getting the uniquevalues from field option.

* Fixed bug where if more than one uniquevalsfromfield was used in an expression Only one would populate the dropdown.

This appears to still be the case IF the layer with more than one is the first layer listed in the eSearchWidget.xml. It will populate one of the dropdowns only. Used to be I had to select a different layer/expression, then back and it would populate the "next" box, then had to do it again for each value that was using uniquevalsfromfield. Well, now when I navigate back to it, it will populate ALL of them. OR, if I set that layer as something other than the first layer, it will populate them all when I "choose" it from the dropdown. So, it appears as if it is not populating ALL of the uniquevalsfromfield dropdowns at once if the layer is loaded by default, but only if the layer is selected by the dropdown.

R_

RhettZufelt

As far as the uniquevalsfromfield adding a blank I had this fixed at one point them made some more code changes to account for a possible empty string value being in the data and I broke it again. But I now have it fixed again. Please re-download the widget.

This brings up a good point/question: What happens if I have the value "all" in my data? Will selecting "all" just query them, or everything in the list?

R_

RobertScheitlin__GISP

Rhett,

This confusion is why I was hesitant about adding the "all" to the unique value list when you asked for it. So what I ended up doing is when I see the all chosen in the unique value dropdown I just do a 1=1 query (basically giving you everything as that is what all unique values would be).

BTW Version 3.0.14f is now available with the fix for the first query layer having multiple uniquevalsfromfields

RhettZufelt

Rhett,

This confusion is why I was hesitant about adding the "all" to the unique value list when you asked for it. So what I ended up doing is when I see the all chosen in the unique value dropdown I just do a 1=1 query (basically giving you everything as that is what all unique values would be).

I see that you are adding "all" to the list, but the query is sending "allu" and when it sees "allu" it sends "1=1". Couldn't one just modify the "all" to something like "all values" and the query to "__allvals__" (or something that will probably never be in the data like "allu" ;o), that way, if the value of "all" is in the data, the pagingquery will find it and add it to the list but you could always select the "all values" option also.

As far as the uniquevalsfromfield adding a blank I had this fixed at one point them made some more code changes to account for a possible empty string value being in the data and I broke it again. But I now have it fixed again. Please re-download the widget.

So, did you have to un-do this "fix" to get it working correctly as I see we can not search for empty strings (or spaces or nulls) as a value using the uniquevals or userlist options. (uniquevalsfromfields no longer captures the NULL values)

BTW Version 3.0.14f is now available with the fix for the first query layer having multiple uniquevalsfromfields

Yep, seems to be working fine.

However, in this version if one clicks on the Clear button before a search, it throws a null values error (at least with debugger flashplayer). If ANY search has been performed, even if cleared, then you can hit the clear button all you want without the error.

also, it appears that if you only have one search layer (either layer(s) or table(s)), you do not get the new "add to selection", "remove from", etc. options.

R_

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.