Enhanced Search Widget Version 2.23.1 - 11/22/22

[#1]

Live Preview Site

Web AppBuilder for ArcGIS | Help - Enhanced Search widget

List of the latest enhancements and changes:

1. Fixed issue with Spatial Relationship settings

Older enhancements or changes

Check the "Older enhancements or changes.txt" in the download for a complete list.

Older Versions

Last 2.21 version

Last 2.17 version

Last 2.13 version

Last 2.12 version

Last 2.11 version

Last 2.9 version

Last 2.7 version

Last 2.6 version

Last 2.5 version

[deleted-user-dbQhBq-o3nyM]

Robert​, was this ever addressed in the latest release?

[RobertScheitlin__GISP]

Jordan,

   No it is already done in the 1.3.0.1 release but I am still working on other enhancement requests and am not ready to release yet. ETA this week or next.

[deleted-user-dbQhBq-o3nyM]

Robert,

Thank you. I don't know who thought that it was a good idea to add an ampersand to our zone abbreviations. Obviously they were not thinking the way the computer does.

I suppose I will wait until the release then. Thanks again.

[SethLewis1]

Robert,

If the following has been asked, please let me know but I didn't locate any search results on the matter.

Is Enhanced Search compatible with secured map/feature services? And if so, would you point me to the relevant section of the .js that handles the Server authentication?

Thanks

[RobertScheitlin__GISP]

Seth,

   In the JS API all secure service handling is done through the Identity Manager or handled through a Proxy. Are you having an issue with a secure service?

[Anonymous User]

Robert Scheitlin, GISP​

I realized there is a feature that will substantially increase eSearch power for us, and anyone else with a service that has a lot (100+) layers spread over many groups (about two dozen for 600 layers on our site).

Groups. Submenus of groups on the Search Layer menu.

Thoughts?

Here is what I have now:

Here is what I propose, at least one level of groups:

don't mind the ugly looking interface "buttons" I mocked up in MS Paint!

eSearch "Search by Shape" is the absolute best way I have found yet, to "Identify".  I only have the Identify still because of its ability for "All Visible Layers.

Another way to solve this is "All Visible Layers" functionality, like Identify has, but I know you said "All Visible Layers" would be extremely complicated to add to eSearch by Shape.  So I propose either Groups (one level of grouping at least) unless a way to incorporate All Visible Layers ability becomes feasible.

I know this is a heavy ask.  Thought I'd throw it out there though and see what you and the eSearch braintrust here thought.

eSearch is still integral to our site.  Currently I've put the top 25 most useful layers in it, and it's great.

Sorry for so many suggestions... our site basically revolves around this tool though! I have a legion of users  about to use our internal flagship site built on this tool and since it's the kitchen sink viewer it's got all these hundreds of layers!    (Yes... if you are thinking...task-based viewers etc..and those are next on the to-do list.. but we also need our kitchen sink viewer for a few reasons)

[RobertScheitlin__GISP]

Kevin,

   There is no Dojo UI dijit out there that would support that type of UI. Currently I can not think of a practical coding workflow to accomplish this that would justify the level of effort to implement it.

[Anonymous User]

Robert, thanks for the reply and consideration.  I understand.

I have successfully created a 'workaround' of sorts.  I placed 'dummy' layers as 'headers' to section the menu.

I used a layer that has only one feature way out in the ocean. (This approach requires a valid layer with one field).

It works!

One thought Robert:

Perhaps you could codify this and make a special flag on the layer to make it a 'header layer' and in that event, the user has but one piece of info to enter: the text string for the title.   Ideally I'd like these headers to be bold or a different color etc that stands out, but the way I've got here is good enough for now, using CAPS and ---dashes.   Hope this is useful. In fact, looking at it now I'm quite pleased!

[SethLewis1]

Robert,

I'm able to add a secured service but when eSearch launches for the first time in a browser session, I'm challenged for the role credentials that were originally used to secure the service.

Am I correct in my thinking that passing a token via proxy (somewhat similar in logic to this discussion Internal ONLY Web Map Sharing Issues ) would fix the issue?

[RobertScheitlin__GISP]

Seth,

   Yes, that is correct.

[StefanP__Jung]

It would be very nice if you could also search for Attributes of Stream Layer which are currently visible in the map.

[RobertScheitlin__GISP]

Stefan,

   I was not aware that a stream layer provided a query capability. When I check the esri samples stream layer the only capability I see list is subscribe.

[StefanP__Jung]

Correct, that would make it a lot easier with a query capability.

You have to develop the code by yourself and search on client side.

[RobertScheitlin__GISP]

Not sure that is even a possibility.

[glennhazelton]

robert

i just was trying to configure a new query using your latest version.

when i go build the expression and ask for unique values the dropdown never populates.

the queries i built previously still work.

i have tryed a couple different layers with the same result.

any ideas how to track the issue down.

[glennhazelton]

this is what i am seeing in the F12 display when i click to add an expression.

[RobertScheitlin__GISP]

Glenn,

   Well I thought I had tested this thoroughly... Make this change to the SingleValueEdit.js at those lines

//	this._getValue();

var value, value1, value2;

if(!this._valueObj){

  value = "";

}else{

  value = this._valueObj.value || "";

  value1 = this._valueObj.value1 || null;

  value2 = this._valueObj.value2 || null;

}

[glennhazelton]

thanks Robert

the new version works great!!

have a good day

Glenn

[Anonymous User]

6.  Added check all for "popup only"

Sweeet.  You just saved me many hours of work!

I just installed it and it works great so far in our WAB 1.2. It reads the existing config json perfect.  In fact, it even fixed an issue. The release from December didn't work on our roads layer for some odd reason Layer: Local Roads (ID: 41)  but now it does.

The new way you show what area you'd selected with the graphic, is really cool Robert. Very nice interface design and feedback.  Customizable symbology per layer, awesome.  I still propose a fourth category where it takes the server symbology and then puts a halo or highlight around the symbol, would be good. (for selected features from a layer to stand out when the layer is turned on. But still have original symbology)

Ability to remove results, just wow.  It just gets better. Our municipal users are really going to get some work done with this. Get in, get some data, get out and do good things.

[MassimoBisogno]

Hello Robert, I installed version 1.3.0.1 of Enhanced Search Widget. I think there is the problem again on codedvalue domain for the fields of long type, already reported to me a few months ago and fixed in the version 1.1.1

List of the latest enhancements and changes:

...

Fixed bug with Coded domains that use numeric fields not displaying domain description.

...

You can take a look?

thank you

Massimo

[RobertScheitlin__GISP]

Massimo,

   I have just tested version 1.3.0.1 using a map service that has a long field with a coded domain and it show up just fine...

[MassimoBisogno]

Robert i tested with the layer of a FeatureServer and is ok, but with same MapServer layer i have a problem.

[RobertScheitlin__GISP]

Massimo,

   Strange it was a Map Service that I used to test. Is there any detail you can share about the field values or specifics about the domain or better yet is the service public? If not maybe you can export out a small sample of the data to a FGDB for testing.

[MassimoBisogno]

Hi Robert this is fgdb extract.

https://comunemonza-my.sharepoint.com/personal/mbisogno_comune_monza_it/_layouts/15/guestaccess.aspx...

thank

Massimo

[BrianO_keefe]

Curious. Is there anyway to remove the popups that are created FROM the eSearch widget itself? We have configured highly customized pop-ups on the AGOL side of things and it confuses our users to have multiple pop-ups display presenting redundant (or duplicated) data.

[RobertScheitlin__GISP]

Brian,

   Currently no. I will consider this for a future release though.

[RobertScheitlin__GISP]

Massimo,

   I did not have any issue with the data you provided. See the image:

[MassimoBisogno]

Thanks Robert will check better what happens

[deleted-user-dbQhBq-o3nyM]

Robert thanks for the awesome responsiveness. I updated my WAB's eSearch yesterday and everything works great.

Thanks again!

[MassimoBisogno]

Hello Robert the codedvalue domain issue occurs when I select the option Unique instead of option Value in the form Update Expression. I do not know if this is actually a bug or a desired behavior. Thanks for your time

[RyanKelso]

Can this widget be updated to a newer version, in an existing app, but with keeping the old config file?  So I don't have to re-configure everything?  Or will it break something...

[RobertScheitlin__GISP]

Massimo Bisogno​

   OK, I see the issue now. I never tough there would be a need to use unique when the field already has a domain attached to it, so I do not lookup the domain values when using unique. I will look at addressing this in the future, but the real solution is not to choose unique when using a field with a domain.

Edit: OK I see the usefulness of have unique values even from a domain. A scenario would be where you have a large domain and currently on 10 out of the 50 possible coded values are used. I have fixed this for the 1.3.0.2 release.

[RobertScheitlin__GISP]

Ryan,

   sure as long as there was no breaking changes to the json in between the versions you are using and updating to.

[RyanKelso]

Hey Robert, Result Item Sorting is still not working in 1.3.0.1.  I followed the instructions from your post on November 12th for the fix.

[RobertScheitlin__GISP]

Ryan,

  Thanks for the heads up I will address this in 1.3.0.2.

[RyanKelso]

One other thing I've run into.  I configure an attribute search using the BETWEEN operator.  I enable "Value is required to be entered to enable search" and I enable "Ask for values".  The search executes properly using the default values that I've configured, but when I change the values, it still returns the same results as when using the default values.  So it doesn't seem to be reading user input values.

[haThach]

Robert,

I'm currently using your enhance search 1.3.0.1 widget in Web Appbuilder. Loves how you transition all the functionality over to be use in the Web Appbuilder environment. With this enhance search widget, is there a way or code I could use to make a layer visible? In Flexviewer, you happen to provide me with just this code "map.getLayer ("Your Layer Name").visible = true;". I was wondering if this functionality carry over to Web AppBuilder.

See below of what I'm trying to do from my old production flexviewer....

Thanks,

Ha T

[RobertScheitlin__GISP]

ha T,

   Sure try this:   this.map.getLayer('DSIC Projects').setVisibility(true);

[haThach]

Thanks Robert for a quick response.

Can you tell me the file name and location of where this code should be added? Thanks again.

[RobertScheitlin__GISP]

ha T,

   Basically the same as it way in the flex version in the main widget.js file in the onOpen function

[haThach]

It works like a charm. Thanks Robert

The only different in WAB is that I have to replace "DSIC Projects" with AOL layer ID "PA_MReplacement_8111".

If anybody are interested in getting your OAL layer id. Here's how....

1. Orig.

http://www.arcgis.com/sharing/content/items/(Enter Webmap Layer ID)/data?f=pjson

2. Change to

http://www.arcgis.com/sharing/content/items/0xxa61a2fcb2a4f87b35788e9ee906fxx2/data?f=pjson

**Note: Your Webmap must be shared with everyone.

3. Copy all the text to notepad ++ and search for your layer. See below

Thanks,

Ha T

[haThach]

Robert,

This is a related question, Instead of creating a duplicate search widget just to turn a specific layer on. Are there an option to setup the code to work just for a specific Search Layer list when you select one?

Thanks,

Ha T

[RobertScheitlin__GISP]

Ryan,

   I see the issue and will have this fixed in 1.3.0.2. Thanks for the info.

[RobertScheitlin__GISP]

ha T,

   Sure just put some logic in the onAttributeLayerChange function in the widget.js to check for that particular search layer name (i.e. if(this.config.layers[newValue].name === 'Project Search') { //then do something })

[haThach]

Robert,

I tried adding this and it didn't do anything. Can you help?

[RobertScheitlin__GISP]

ha T,

   I am not sure what is wrong then. You should probably put a console.info('got here'); into the if and see if you are actually get inside the if.

[TomPike]

Hi Robert,

Thanks for all these great widgets!

I experience some problems with eSearch widget in Launchpad theme - attribute table doesn't open with results, unless Attribute Table widget is added on its own. Is it normal behavior/known bug with Launchpad theme? I recall this theme was buggy in previous release as well, unfortunately I find it most suitable for my app. Please comment...

[RobertScheitlin__GISP]

Tom,

   Hmm...  I just tested the eSearch widget 1.3.0.1 and WAB 1.3 and it opened the Attribute table widget automatically when searching a layer that was defined to "Add Result as Operational Layer" and "Show in Attribute Table Widget".

[glennhazelton]

Robert,

i just found an odd bit of behavior. Maybe you know if it is a 'feature'.

i have build a WAB app and downloaded it (it uses your latest esearch and the 1.3 (latest) version of the WAB.
after downloading i unzip and copy the app to the wwwroot directory

when i open the downloaded app and zoom to an area and then close and re-open the url

both IE and Chrome zoom me to the last location i was viewing and display whatever layers i had turned on or off.

this isn't happening with my development enviroment, but i have 1.2 install there still.

any ideas?

i have cleared the history of course.

glenn

[RobertScheitlin__GISP]

Glenn,

   The restoring of the last map extent and layer visibility was something that was introduced in WAB 1.3 it has nothing to do with eSearch and currently is Not a configurable feature.