Latest Contributions by AdamDrackley

The Javascript API can be pretty bad at rendering complicated symbology on FeatureLayers; Unfortunately this might be what you're running up against. One sneaky way to do it is to add the same service as a MapService, so that the layer gets rendered properly on the server-side, and also add the same layer as a FeatureService, but give it an empty or invisible symbology.  This makes the layer selectable, and you get to see your complex symbology from the MapService layer.  Just a thought. ... View more

Have you made the code change to your AttributeTable Widget described here, Babatope?  What version of the WebAppbuilder are you using?  From your posts above, it sounds like you're able to configure the AttributeTable widget for your LocalLayer layers, but your configuration isn't actually being used by the application, does this sound correct? ... View more

Hey Babatope, try removing the Attribute Table from your App entirely before adding and configuring the LocalLayer widget.  Make sure that the actual Configuration file for the Attribute Table widget under the /configs/ folder is gone.  It's been awhile since I tried this, but I think when you re-add the Attribute Table widget after configuring LocalLayer, it will instantly read any layers present in the map and give you some visibility/configuration options for your LocalLayer layers. Let us know if this works! ... View more

What version of the WAB are you using, John? ... View more

Thanks Rebecca; Reading your helpful document, I'm encouraged to see that this functionality is on Esri's radar for WAB as well.  At the very least, hopefully this widget can be a get-you-by until Related Editing functionality is built into the WAB by default. ... View more

Version 2.0 has been released.  Give it a try Mike; You'll likely still encounter the same menu issue from before.  I'm sure I'll eventually fix that menu, but I tend to just write in the field name myself. ... View more

It looks like I didn't have autorefresh capability enabled properly for Dynamic Mapservices, thanks for finding this Michael.  Give the candidate version below a try.  Note that you should also be able to specify decimal values for the timeout if you want it to be less than a minute before refreshes. GitHub - cmndrbensisko/LocalLayer at LocalLayer2.0 ... View more

Is this for a Feature Layer, Michael? ... View more

Good catch!  I hadn't revisited the text of the original post since it originally went out over a year ago.  Hopefully it hasn't dissuaded anyone from using the widget, but I've updated the post accordingly. ... View more

Hey William, I've just slipped a simple fix into the candidate that should enable Viewing Attachments on Dynamic Layers.  Feel free to give it a try on your end. GitHub - cmndrbensisko/LocalLayer at LocalLayer2.0 ... View more

Hey William, thanks for your post.  I don't think we've done much to crack the attachment nut yet, but we can certainly take a swing at this in the latest candidate widget.  To make testing easier, do you happen to have a public-facing MapService with attachments? ... View more

Haven't tried Robert, but I think the three "-1"s are necessary.  If you peek into jimu.js/LayerInfos/LayerInfoForMapService.js, you can see it gets pretty nutty. Line 633:       if(visibleLayers[0] === -1 &&          visibleLayers[1] === -1 &&          visibleLayers[2] === -1) {         this._subLayerVisibleChanged();         this._isShowInMapChanged2();         return;       } Line 644: var visibleLayersForSetVisibleLayers = [-1, -1, -1]; Line 211:       var ary = [-1, -1, -1], index; The WAB really seems to be marching to the undocumented beat of its own drummer on these; The best I think we can try to do in our own widgets is emulate it as best as possible. ... View more

I've run into this kind of behaviour before with the LocalLayer widget.  It seemed like the Web AppBuilder's idea of a 'visible layer' differs somewhat from what's described in the API doc. Currently, the SaveSession widget attempts to 'set' layer visibility using the following code on line 615 of Widget.js:                     if (layerSettings.visibleLayers && layer.setVisibleLayers) {                         layer.setVisibleLayers(layerSettings.visibleLayers);                     } For some reasons related to how the jimu.js libary interprets layer visibility, I'm finding that changing this section to use the code below results in the LayerList widget 'properly' interpreting which layers should currently be visible.  This code is similar to some code we use in the LocalLayer widget as well to accomplish the same purpose.  As an example of the WAB's oddness, note that in order to properly interpret a layer as truly 'off', it requires an array consisting only of three '-1' values.  Any light that could be shed on this by anyone would be great!                     if (layerSettings.visibleLayers && layer.setVisibleLayers) {                         var visibleLayers = lang.clone(layerSettings.visibleLayers);                         if (layerSettings.visibleLayers.length == 0) {                             visibleLayers = [];                             visibleLayers.push(-1);                             visibleLayers.push(-1);                             visibleLayers.push(-1);                         }else{                             var removeItem = []                             array.forEach(visibleLayers,function(visibleLayer, index){                                 if (visibleLayer == -1){                                     removeItem.push(index)                                 }                             })                             for (var i = removeItem.length; i-- > 0;){                                 visibleLayers.splice(i, 1)                             }                         }                         layer.setVisibleLayers(visibleLayers);                     } In any case, this enhanced code works well for me.  If other adventurous people want to give it a try, I'd be happy to fork the repo for an enhancement if it would benefit the widget. ... View more