Latest Contributions by AdamGebhart

Alix Vezina‌ - thank you for the reponse.  Just to clarify though, does your example refer to a hosted feature layer?  I am working with an ArcGIS Server feature service and not a layer hosted in AGOL or Portal. The web map consumed in a WAB 2.13 (Developer) app resides in AGOL. ... View more

Thank you for the explanation Alix.  I can relay this information to our users if they have questions as they use the widget. Thanks again. ... View more

I believe we do but I don't know for sure as I have not heard from our few ArcReader users since my original posts.  I'm guessing at this point they just know what the best work around is. In the near future we will transition them away from ArcReader maps to a web app. ... View more

Hi Tom Sellsted‌ I updated to Developer 2.13 earlier this week and was informed yesterday that the polyline feature isn't showing/capturing the individual segment length.  Instead, it's just providing the total length/perimeter.  Are you aware of this or can you replicate it? Below you see 2.12 (left) and 2.13. ... View more

Thanks for the information and tip, Robert.  That works nicely. ... View more

Robert Scheitlin, GISP‌ Hi.  Is it possible to disable the Zoom to and the Clear selected links in the ActionPane or ActionList?  I've tried do it via commenting lines 13-16 or 14-15 in widget.html and lines 113-115  in widget.js, but both of those attempts kicked back a load error for the widget. Below is an image showing the problem I'm trying to avoid.  The Layer List widget is in the Header Controller while the Popup Panel is On Screen.  You can see both are open, with the Layer List 'over' the Popup Panel, but the Zoom to and three dots in the Panel's Action area bleed through.  Is there a transparency setting of the on-screen widgets I need to adjust? I'm using 2.12. ... View more

I am working in WAB 2.12 and thought I would put in one post all of the steps needed to accomplish the symbology update (or what works for me) based on the previous posts.  Thank you to everybody who has helped. First though, click and vote up this ArcGIS Idea that Greg Bazhaw‌ posted to ask ESRI staff to "Change selection color in Search Widget in Web AppBuilder."  It would be great if we could do this in the configuration window or just have an easier way of doing it. Change the Search widget symbology in WAB 2.12 1)  Add 'esri/symbols/jsonUtils', to define and add jsonUtils in function according to Robert Scheitlin, GISP post on July 7, 2016 (see here).  Changes are on lines 38 and 54. 2) Added lines 324-329 per Kyle Schwizer‌'s post on October 31, 2018, from within this thread.     Commented line 327 per David Coley‌'s post on April 10, 2019, also from within this thread. 3) Comment lines 351-386 per David Coley's post on April 9, 2019, also from within this thread. 4) Note - this is NOT a change but I want to point out that Kyle's post from October 31, 2018 also states to comment "this.searchDijit.clearGraphics" (line 492 below).  That was already a comment in 2.12. 5) Added "highlightSymbol" settings to the Search config json.  See lines 42-57 and remember to add the comma after "query" on line 42 per Robert S.  My settings create a red circle around an address point. One tip to pass along is in reference to item 2 above.  I have two or three searches configured in all of my apps, some search on a point layer and others on a polygon layer.  What I noticed was if I didn't comment line 327 (see item 2) then my polygon searches returned the symbology for the points and polygons.  That's illustrated below.  I should only be seeing the red parcel border for a parcel search.  Commenting line 327 stopped that.  (I did not notice any instances where a point search returned both the point and polygon symbology).                                                           ... View more

Thanks.  I've done a little more testing of the Search and eSearch widgets in the 'new' version of 2.12 on my PC and haven't had any problems.  I even copied and pasted the eSearch config from my existing deployed app and it came in just fine.  Something apparently is just off with the other 2.12 I have on this PC or I've unintentionally made a subtle change to it that prevents eSearch from operating properly.  Thanks again. ... View more

ArcGIS Server = 10.6.1.  We have Portal 10.6.1 installed on another server but we're not running anything off it right now.  Everything is coming from AGO or AGS. I installed WAB 2.12 on a laptop last Friday and in a test app there I am able to get all of your default searches to work.  Only one of them works in the version on my PC.  Weird.  My service I'm trying to use in eSearch won't work in WAB on my PC but it seems to be working on the laptop, and the same goes for another service I created this morning to test things further.  I am currently installing another instance of WAB 2.12 (in a different location) on my PC to see if I can replicate the problem there. We've been having problems with the speed of the Search widget in our WAB 2.9 apps ever since we had the server updates two weeks ago.  Results used to populate within two seconds at worst and now we're waiting 10-15 seconds at times.  There were some changes (field length and type I believe) to our parcels layer that pre-dated the server updates but those same searches were running just fine before we went from 10.4.1 to 10.6.1, and the fields that were modified are not field I use for searching.  I have an open case with ESRI on that matter.  Note that I have overwritten and completely republished our services since we went to 10.6.1, hoping a fresh start on them would cure the issue(s) but to no avail. I'm just trying to eliminate the source(s) of the problem and was curious if you had come across any similar issues.  Thanks. ... View more

Thanks.  Do all three of Robert's default searches work when you add eSearch to a new app?  I'm most surprised by the fact that only one of three work on my end. ... View more

Robert Scheitlin, GISP‌ Sorry to reply to my own comment but I want to pass along that I was able to copy and paste the previous Identify config (from 2.9) into 2.12 and have everything work as it was configured.  Recall from my first post that I've done that in the past for eSearch and had things been ok, just not this time.  Also, a few of the REST endpoints being hit in the Identify widget are also being hit in the eSearch widget, but they're not working eSearch like they are in Identify. ... View more