Latest Contributions by NicholasBarger

Hi Larry, I’m using WAB Developers Edition. I placed the widget folder (ZoomPrevNext) in the WAB/client/stemapp/widgets folder. I created a new app but the widget never transferred over to that app. So I manually copied it to my app… WAB/server/apps/xxx/widgets. The next thing I did is copy the code in the docs folder as it appeared into the main config.json file. I placed the code at the end of the widgetOnScreen section. I made sure I placed a comma after the last widget and removed the comma from your cade as it was the last widget… see below. I would send a link but I am unable to download the app after adding the code. It seems to make WAB act very strange. I end up having to use back buttons and refresh the page manually. { "uri": "widgets/TimeSlider/Widget", "visible": false, "position": { "bottom": 55, "left": 7 }, "version": "1.2" }, { "uri": "widgets/Swipe/Widget", "visible": false, "position": { "top": 145, "left": 7 }, "version": "1.2" }, { "uri": "widgets/ZoomPrevNext/Widget", "position": { "left": 7, "top": 70 }, "version": "1.1.0", "id": "widgets/ZoomPrevNext/Widget_119", "name": "ZoomPrevNext", "label": "Zoom Prev Next", "positionRelativeTo": "map } ] }, "map": { "3D": false, "2D": true, "position": { "left": 0, "top": 40, "right": 0, "bottom": 0 }, ~ Nick ... View more

Hi Larry, Do you have any additional installation instructions for this other than the info in the docs folder.  I placed the widget folder in the standard location but it hangs up my WAB and never completely loads the page. Have you used this widget with the Local Layer widget? ... View more

It doesn’t have to be. I had another app that was not working. My main service was working fine, but I had a weather service in the app as a secondary service. That caused me problems as well. Try removing services / adding services one at a time until the eSearch tool breaks. Then you know which service it is. You may also want to continue to see if other services cause it problems. ~ Nick ... View more

Andrew, Do you have multiple instances of the same layer in your service? For example, do you have multiple street layers? I had a similar problem as this and found that if the service had multiple copies of the same layer that you needed to group one of the duplicate layers for the attribute table to work correctly. I used a duplicate of several layers for labeling purposes in my apps. I found that while ungrouped I saw the same behavior as your site. ~ Nick ... View more

So, Based on my preliminary findings this morning I'm thinking this problem is a service related problem with the Local Layer Widget. The only difference between this service and the other is that I do not have groups... let me explain.  To allow for more control over labels I add streets, buildings, and parcels into my project multiple times.  One Buildings layer will have the geometry completely clear, but I will turn on labels for address.  I set up visible scale ranges to further control the draw time.  I do the same thing for address ranges and street names on our street center lines, and owner names and parcel number on the parcels layer. On all of the services that worked correctly I had these duplicate layers grouped (as Labels) in my service.  In this service I did not.  They were all listed in the TOC as is.  They had different names... i.e. Street Name, Building Address, Streets, Buildings, etc.  Once I grouped the Labels (duplicate layers) and republished the service the eSearch widget worked... more specifically the attribute table was populated with the information from the eSearch tool.  I narrowed this down to a service by adding a working service into the WAB Local Layer widget and using my other service (not working) into the eSearch widget.  This produced the correct results. Amy Knight​ - I'm curious... do you have multiple instances of the same layer in your service? Thanks, Nick ... View more

Robert, I'm thinking this is serviced based and here is why... I tried to duplicate a working app using WAB.  The copy worked.  As soon as I changed the service in the Local Layer Widget to one of the services that are not working then the eSearch widget breaks.  As a further test I used a working service in the local layer widget and the service that didn't work in the eSearch widget and the search successfully opened the attribute table and populated it. I have yet to figure out what is different between the services. ... View more

{ "layers": [ { "name": "Parcels", "url": "http://gissites.co.centre.pa.us:6080/arcgis/rest/services/WEBIA/MapServer/9", "definitionexpression": "", "spatialsearchlayer": false, "zoomScale": 10000, "shareResult": true, "addToAttrib": true, "expressions": { "expression": [ { "alias": "Tax ID Number", "textsearchlabel": "Search by Tax ID Number", "values": { "value": [ { "fieldObj": { "name": "TAXIDNUM", "label": "TAXIDNUM", "shortType": "string", "type": "esriFieldTypeString" }, "valueObj": { "value": "" }, "prompt": "TAXIDNUM contains", "textsearchhint": "32-102-,281-,0000-", "sqltext": "Upper(TAXIDNUM) LIKE Upper('%[value]%')", "operation": "stringOperatorContains" } ] } } ] }, "titlefield": null, "fields": { "all": false, "field": [ { "name": "TAXIDNUM", "alias": "TAXIDNUM" } ] }, "links": { "link": [] }, "showattachments": false, "layersymbolfrom": "config" }, { "name": "Buildings", "url": "http://gissites.co.centre.pa.us:6080/arcgis/rest/services/WEBIA/MapServer/8", "definitionexpression": "", "spatialsearchlayer": false, "zoomScale": 10000, "shareResult": true, "addToAttrib": true, "expressions": { "expression": [ { "alias": "Address", "textsearchlabel": "Address", "values": { "value": [ { "fieldObj": { "name": "ADDRESS", "label": "ADDRESS", "shortType": "string", "type": "esriFieldTypeString" }, "valueObj": { "value": "" }, "prompt": "ADDRESS contains", "textsearchhint": "420 Holmes St", "sqltext": "Upper(ADDRESS) LIKE Upper('%[value]%')", "operation": "stringOperatorContains" } ] } } ] }, "titlefield": null, "fields": { "all": false, "field": [ { "name": "AID", "alias": "AID" }, { "name": "ADDRESS", "alias": "ADDRESS" } ] }, "links": { "link": [] }, "showattachments": false, "layersymbolfrom": "config" } ], "initialView": "text", "multipartgraphicsearchchecked": false, "addpointtolerancechecked": false, "keepgraphicalsearchenabled": true, "autozoomtoresults": true, "toleranceforpointgraphicalselection": 6, "bufferDefaults": { "bufferUnits": { "bufferUnit": [ { "name": "UNIT_FOOT", "label": "Feet" }, { "name": "UNIT_STATUTE_MILE", "label": "Miles" }, { "name": "UNIT_METER", "label": "Meter" } ] }, "bufferDefaultValue": 5, "bufferWKID": 102003, "simplefillsymbol": { "color": [ 1, 185, 253, 128 ], "outline": { "color": [ 1, 185, 253, 204 ], "width": 1, "type": "esriSLS", "style": "esriSLSSolid" }, "type": "esriSFS", "style": "esriSFSSolid" } }, "spatialrelationships": { "spatialrelationship": [ { "name": "esriSpatialRelContains", "label": "entirely contained in" }, { "name": "esriSpatialRelIntersects", "label": "intersected by" }, { "name": "esriSpatialRelEnvelopeIntersects", "label": "intersected by envelope of" } ] }, "graphicalsearchoptions": { "enablepointselect": true, "enablelineselect": true }, "symbols": { "simplemarkersymbol": null, "picturemarkersymbol": { "url": "/widgets/eSearch/images/i_search.png", "height": "20", "width": "20", "type": "esriPMS", "angle": "0" }, "simplelinesymbol": { "type": "esriSLS", "style": "esriSLSSolid", "color": [ 255, 0, 0, 204 ], "width": 2 }, "simplefillsymbol": { "color": [ 255, 0, 0, 128 ], "outline": { "color": [ 255, 0, 0, 204 ], "width": 2, "type": "esriSLS", "style": "esriSLSSolid" }, "type": "esriSFS", "style": "esriSFSSolid" } } } ~ Nick ... View more

I also get this... Error in parsing value for 'line-height'.  Declaration dropped. test and when I open the Attribute Table first I get this... Error in parsing value for 'width'.  Declaration dropped. test Error in parsing value for 'height'.  Declaration dropped. test I still get this error... TypeError: a[0] is undefined init.js:1299:101 but the table is populated. ... View more

Here is a link to a test web app. ArcGIS Web Application Here are the errors from the consol TypeError: a[0] is undefined init.js:1299:101 TypeError: this.tabContainer is null This error is followed by a lengthy stack trace ... View more

Just tried adding another search and its still not working.  Initially it did... but now nothing. ... View more

Hi Robert, I'm running into a strange problem.  I was using the previous version of the eSearch widget and I am making the jump to the latest version.  I have been hunting for a solution to this for several days now.  I have even tried recreating all of the sites from a backup (Pre 1.1.6) and I keep getting the same results.  So here we go... I started updating my apps with the new eSearch widget.  The first 3 widgets that I updated worked perfectly.  They were all updated the same way.  Once I hit the 4th App things began working poorly for me.  I am trying to update the app the same way as the previous 3 but it appears that the attribute table is no populating.  It opens but it is blank.  If I close it and rerun a search it opens and then places the table of the selected set but never return any results.  I get caught in the spinning loading symbol.  I close it  and clear the search a second time, and re run the search and now there are 2 table open.  Sometimes, of I leave run long enough one of them (the first in the list), will have data.  I have found that if I open the attribute table prior to ever running a search then everything works correctly. I thought that there may be something wrong with that app so I tried another app....same results. Any thoughts?  I read the problems directly above.  I'm going to add another search layer and see if that corrects things. This widget is really coming along.  Love it! Thanks, Nick ... View more

Hi Tim, I found the code.  It appear that the info window resize was being set permanently.  I commented out all of the infoWindow calls and it worked.  I also commented out just the resize lines and then the popups worked and the eSearch popups were the correct size. ... View more

Hi Tim, I have a question.  Can you give me an idea of how to disable the popup function in your Location Widget?  I have an idea about the popups with this tool.  I'm looking for it now but I figured you had a better idea how to disable this. The reason for this is I believe this widget is resizing my popup window permanently.  In other words, when I use the eSearch widget my popup window is the correct size.  I switch to the Location Widget click on the screen returning results in the popup window.  I then go back to the eSearch tool and the popup window is the same size as in the location window. Since I really have no need for the popup I was looking to disable it. Thanks, Nick ... View more

That makes sense…the local layer widget is calling the built in popup. I’m guessing that the Location Widget uses a common class that is causing the problems with the Popups. ~ Nick ... View more

It looks like there is one more incompatibility that I am running into.  It appears that the location widget resizes the popup window to about 1/2 to 1/3 the original size.  Everything appears to work fin until that point. ... View more