Latest Contributions by DavidColey

sounds good.  I'm moving to 10.4 shortly in my dev environment and will report any difficulties,etc ... View more

No you're right, I just wasn't quite sure if you were strictly referring to the online use case which obviously you are.  Sorry I can't be of more help ... View more

Are you sure you have sync capability enabled on your feature service and/or hosted feature layer? ... View more

I'd check privileges.  I've got 2 deployments going, one with hosted layers only, a second with both hosted and a feature service from my environment.  In both cases the webmap and feature layers are shared to the same group and sync is enabled on the feature layer.  Full create, update and delete are set on the feature layer as well- ... View more

So you are saying that in your web map, you have both hosted feature layers and a feature service from your environment? ... View more

Ok thanks Aravind that's what I thought. Just double checking David ... View more

Hey Robert, did you (or anyone) here have to add the routing, traffic and logistics services to your content? ... View more

Just a quick follow up: I sorted every value pair for every fields array for every feature layer of the Attribute Table config.json such that name; alias; show are in the same order for each.  In my case, for most layers the show value is honored.  For 4 or 5 of the layers, it is not. More info: The visible attributes are the same in my web maps' configure attributes, i.e showing the same attributes in my web maps table as I have the config.json set. ... View more

Oh hey Jamie how are you?  Thanks, yeah I've done all that.  Yes, I am working strictly with publically-shared feature layers in my webmap. In looking at the config.json, the layer infos ordering for the "show" boolean changes.  For example, here is the layer infos for an Open Rezone Petitions poly-layer in my planning services wab: "layerInfos": [     {       "name": "Open Petitions",       "id": "SarcoPlanning_4226_2114",       "layer": {         "url": "https://ags2.scgov.net/arcgis/rest/services/ScOperational/SarcoPlanning/MapServer/17",         "fields": [           {             "show": false,             "name": "OBJECTID",             "alias": "OBJECTID"           },           {             "show": true,             "name": "PetitionType",             "alias": "Petition Type"           },          {             "show": false,             "name": "Shape",             "alias": "Shape"           },           {             "show": false,             "name": "Shape_Length",             "alias": "Shape_Length"           },           {             "show": false,             "name": "Shape_Area",             "alias": "Shape_Area"           }         ]       },       "show": false     }, And for a communications tower point layer:    {       "name": "Communication Towers",       "id": "SarcoPlanning_2620",       "layer": {         "url": "https://ags2.scgov.net/arcgis/rest/services/ScOperational/SarcoPlanning/MapServer/23",         "fields": [           {             "name": "OBJECTID",             "alias": "OBJECTID",             "show": false           },           {             "name": "FEATURETYPE",             "alias": "Tower",             "show": false           },           {             "name": "Shape",             "alias": "Shape",            "show": false           }         ]       },       "show": false     }, Notice how the positioning of the "show" value appears before the name and alias for the petitions layer, but after the name and alias values for point layer.  Ordering shouldn't matter in the layer infos for the values, but the point layer visibility is honored, and the petitions (poly) layer is not.   Obviously I can control visibility in my services, but that's not really the point, is it?  It's just very buggy, maybe I can find some help at Dev next week- ... View more

Hi again all - sorry to generate my own reply, but has anyone else had issues with the Attribute Table and column visibility settings? ... View more

Thanks very much Robert, that's what I thought too.. for now anonymous access is behaving well but I'll still need to get my proxy setup with one of my named users, I think. ... View more

Thanks, I'm still a little confused.  I expect my WAB edition to use my machine name and node.js port, which it does.  But my previous deployment at 1.2 didn't require anonymous access to our org, and I wasn't using  the proxy.  "Show details" went directly to my rest page.  Looks like I'm going to have to work a little harder.  I need to get proxy set up anyway . . . I'll post back my results David ... View more

Thanks again Robert - the deployed app is located at: ArcGIS Web Application All layers and app is shared with Everyone. The deployed app is registered, config has appID. The redirect uris are pointing at my local machine. Proxy settings are set to false as I haven't finalized my urls     "httpProxy": {         "useProxy": false,         "alwaysUseProxy": false,         "url": "",         "rules": []     }, Interesting behavior: Internally, when I set useProxy to true, user selects show item details and are taken to my Content page, that certainly can't happen... when I reset useProxy to false, user is taken to our sign-in page.  Externally, with useProxy set to false user sees the item details as they normally would see any publicly shared feature service. I'm definitely missing something either with how I've shared the layers or my proxy not being set correctly. Thanks- David ... View more

Thanks Robert, the app is public, let me restore item details visibility in the layerList config and I'll shoot you the url- David ... View more