Latest Contributions by AdamDrackley

Barring any bugs being found, or me finding a fix for the AttributeTable tweak, I don't plan on making any additional changes to 2.0 besides adding to the documentation a bit. ... View more

Thanks Barnaby.  I'm trying to find a clever way to hook into that Attribute Table utils object from the LocalLayer widget, but a solution hasn't presented itself yet.  It may be a devil we have to live with. ... View more

The candidate widget should also work in 1.3 WAB setups as well, without needing to play with the core. It was actually written for 1.3 initially, and I was happy to see it cooperate with 2.0 without any apparent fuss. Feel free to test against both versions. ... View more

Hey all, I've got a candidate version of LocalLayer ready for Web Appbuilder 2.0, and I was hoping to get some intrepid volunteers to help test it!  You'll find the 2.0 branch available at the link below, GitHub - cmndrbensisko/LocalLayer at LocalLayer2.0 For this version, I've endeavoured to remove the need to play with any of those core 'jimu.js' library files to get everything rolling.  Just add the Widget folder to your /widgets/ directory, add an entry for the widget to the appropriate config.json file, and take it out for a spin! ... View more

This is a great widget with some really neat applications.  A quick question; Is anyone else finding that while saved sessions are being re-added to the map properly, the checkboxes in the LayerList widget aren't properly reflecting the new layer visibilities?  I'm seeing this with both ArcGIS Online Maps and LocalLayer configurations.  Let me know if this is just me! Edit; I should mention that I experience this using the 1.3 version of WAB. ... View more

Hey Barnaby, I recieved your email, and upon testing I'm even finding this behavior in the 'pure' WAB built into ArcGIS Online.  I'm going to hazard that this likely isn't connected with the LLW; It looks to be bubbling up from the WAB core. ... View more

I think there's a few things going on here, Justin.  If you're trying to add each of those sublayers as individual Feature Layers, you're likely to run into some limitations in the Javascript API.  To my knowledge, Annotation layers can't be added to Maps as Feature Layers, even in ArcGIS Online.  Layers that use Cartographic Line Symbols for symbology can't be properly rendered as Feature Layers either, because the REST endpoint doesn't provide the symbology information necessary to render these properly on the client-side.  See Dasa's response in the link below, Composite and Cartographic Line Symbols not returned in Renderer objects If you want to add that MapService to your Map, I'd try adding the entire \MapServer endpoint to it as a Dynamic layer. If you still want to break that MapService out into individual layers in your Map, I'd suggest adding multiple \MapServer layers, but configuring the LocalLayer Widget to turn off off all sublayers except the ones you want visible.  IE:  To create a Roads layer, create a Dynamic Layer using the http://gis.co.wood.wi.us/gis/rest/services/FlexGIS/LandRecordsWGS/MapServer url, name it "Roads", and turn the visibility off for all sublayers except layer 15.  For an Annotation layer, do the same thing, name it "Annotation", and turn off all sublayers except sublayer 21. If you want to 'hide' all the sublayers that you've turned off by default from appearing in the Table of Contents, you could use the modified https://github.com/cmndrbensisko/LayerListLite widget instead of the default LayerList widget to ensure that any sublayers which you haven't made visible by default will remain hidden in the TOC.  As a result, despite being a Dynamic Layer, your "Annotation" layer would only contain an entry for sublayer 21 in the TOC. Just some food for thought, hope this info helps. ... View more

I've updated the Readme.md to indicate that the bugfixes constitute a new release (1.3.1), and will update the first post of this thread accordingly. ... View more

Just a note; I ran into this as well during my upgrade.  It seemed that any app whose config.json file contained at least one entry for a widget with a slightly unusual "version" number, such as "1.2.2" or "1.2.0.6", would cause the upgrade to fail for that app.  Fortunately, I didn't need to dig into any of the individual manifest.json files for those widgets; I just changed the entries in the config.json to simple "1.2" version numbers and the upgrade ran fine. The upgraded versions of the apps seem to be all happy-chappy, but I'll update if I find any oddness. ... View more

Right, thanks for refreshing my memory Barnaby.  WAB seems to use an odd method of ensuring that layers with no visible sublayers are rendered properly; Instead of using the typical layer.setVisibleLayers([-1]) approach to set no visible sublayers as specified in ArcGISDynamicMapServiceLayer | API Reference | ArcGIS API for JavaScript​, it seems to expect an array with three -1 values. We tracked this down last year, but I forgot to put it in the latest release.  On line 235 of LocalLayer's Widget's Widget.js file,               if(lOptions.hidelayers.length == 0){                                  lOptions.hidelayers.push(-1);                             } Becomes,               if(lOptions.hidelayers.length == 0){                                  lOptions.hidelayers.push(-1);                  lOptions.hidelayers.push(-1);                  lOptions.hidelayers.push(-1);                } I'll make sure to patch the release with this change immediately. ... View more

I did not; I believe it's only  been tested up to 10.31.  Are you encountering anything on 10.4? ... View more

Thanks Rebecca, I'll be sure to update the original post. ... View more

Just a quick note that a 1.3 version of the LocalLayerWidget has been released on Github, https://github.com/cmndrbensisko/LocalLayer The most important change to be made for WAB 1.3 is the following: 1) In \client\stemapp\widgets\AttributeTable\setting\Setting.js, change line 375 from utils.readConfigLayerInfosFromMap(this.map, true, true) to utils.readConfigLayerInfosFromMap(this.map, false, true) Changing that first 'true' to a 'false' will tell the menu to read all layers from the map as normal, instead of just ArcGIS Online layers. Changing the second 'true' to a 'false' will let the Attribute Table include MapNotes layers from AGOL WebMaps. Some other neat enhancements in this release:      - A Select-All-Fields button has been added to the Popup Menu,      - Using Esri's Symbology playground app, Feature Layers can be given custom symbology and custom labelling (with      scale-dependent labels!) Let me know if any issues are encountered; Hope this is helpful!      - Adam ... View more

LL1.2 will work with WAB1.3, with the AttributeTable caveat mentioned a few posts ago.  A 'pure' 1.3 version will be put together once I have a better idea of the scope of changes to make, but it currently seems to be very few. ... View more

Hey Gabi, hope things are well.  Would you be able to confirm if the link below is the version of the Election Polling Places app you're using? Esri/election-polling-places: An applicatio... - GitHub I've found that esri's boilerplate Locator code can be difficult at times to use with a custom address locator, so I'll point out a few things that are making it difficult for your GeocodeService to work smoothly with this template. 1) Line 37 of Esri's Locator code (/pollingPlaces/js/locator.js) is hardcoded to request a "Loc_name" field from your locator, which I believe only Composite Locators have.      locator1.addressToLocations(address, ["Loc_name"], function (candidates) {... You can replace that "Loc_name" with "*" to just return all fields in your locator. 2) The locator code will only list results that fall within the current extent of the map.  The returned coordinates that I get for looking up "2300 BLOOMDALE, MCKINNEY, TX, 75071 " in your locator look a bit wonky, and I was unable to get them to display even when I had the config file configured more or less correctly.      X: -1.075748460615375E7      Y: 3927251.2575993654      Score: 89.04      Address: 2300 BLOOMDALE, MCKINNEY, TX, 75071 3) With the coordinates and the hardcoding issues sorted out, you should be able to steer the locator from the config.js file.  There's likely better documentation out there on how to configure the config.js file for this particular app, but I configured youra similar to the following.  Note that "SingleLine" in the default data becomes "Single_Line_Input", because this is the actual name of the SingleLineAddressField returned by your service endpoint; http://gis.co.collin.tx.us/arcgis/rest/services/geocoding/ROADS_DualRange/GeocodeServer?f=pjson     LocatorSettings: {         DefaultLocatorSymbol: "images/RedPushpin.png",         SymbolSize: {             width: 25,             height: 25         },         DefaultValue: "2300 Bloomdale Rd., McKinney, TX 75071",         LocatorParameters: ["Single Line Input"],         LocatorFields: ["Match_addr"],         LocatorURL: "http://gis.co.collin.tx.us/arcgis/rest/services/geocoding/ROADS_DualRange/GeocodeServer/",         CandidateFields: "Match_addr",         FieldName: "${Match_addr}",         LocatorFieldName: 'Match_addr',         LocatorFieldValues: ["Match_addr"],         AddressMatchScore: 80,         LocatorRippleSize: 40     }, The "Match_addr" field is just the full name of the returned address, as shown in a json request to your service http://gis.co.collin.tx.us/arcgis/rest/services/geocoding/ROADS_DualRange/GeocodeServer/findAddressCandidates?Street=&Ci… I hope this helps, or at least gets you started. ... View more