Latest Contributions by ChrisWhitmore

There's a server-side aspect as well. I believe the bug was related to support for a new property on map service layers introduced at 10.6.1 (quantizationParameters). Likely this was a latent issue in 3.24 but not too many folks had 10.6.1 yet for it to be exposed.  ... View more

The issue was within the jsapi..updating to the latest WAB dev version once it's released in the next couple weeks should resolve it. It works in agol now because apps hosted in agol (WAB hosted version, map viewer, configurable apps, etc) reference the latest jsapi (which is always updated with a new, incremented version as part of the general agol release). The WAB dev version points to the previous version of the jsapi (or more specifically, the latest version of the jsapi at the time the WAB dev version is made available for download). So once updated to the latest WAB dev version, it will include references to the latest jsapi version which includes this fix. Hope this helps clear up the differing behavior. Cheers,  Chris ... View more

Hi @Map_Sync - unfortunately, no specific tool. I used the needle in the haystack approach and tried to open each layer in the app until it was evident which were private. Your earlier comment regarding the second and a half window before getting bounced to sign is true for the ui experience. However, if you open the developer tools for your browser, you can easily persist the traffic from the initial page load. Which is then basically a log of the network traffic when the app loads all the layers in contains. In my case, I used Chrome's dev tools (CTRL + SHFT + I will open them).  The network tab in dev tools is where the traffic can be found. Selecting the Preserve log option (highlighted) below will keep the log as you go from page to page (especially nice in scenarios like this). I also filtered content to only urls with "Server" in the url, which should be all feature services and map services. Not always the case the offending url is a feature service or map service (or ArcGIS service in general) but most often, it is. And selecting the XHR option will further refine the network traffic to only include cross-domain requests (which basically excludes html / javascript traffic and generally returns service requests). So in this case, filtering on 'server' and XHR is a bit redundant but both are useful on their own.  Once I had the list below, I opened each unique request in a separate tab until it was clear which were unshared.  All of this can be done in Fiddler or any other tool that captures network traffic.  note: the screenshot below is from a sample I set up..not the app Jonathan posted. Cheers Chris ... View more

Hi Allyson - yes, unless you have a tile layer (with automatic tiles enabled) published from the feature layer, you should be able to disable. If not, there might be something going on. Thanks, Chris ... View more

Hi Richard, Would it be possible to get a copy of the original xml you used to import? Can email me at cwhitmore@esri.com if you'd prefer not to post it here. I checked the metadata on some other items in the BLM organization..some of the elements you mentioned seemed to show correctly in the HTML view of the metadata for other items so maybe something specific is going on (here's one I checked where Access Constraints and Distribution Liability seem to come though).  BLM Administrative Unit Office Points  Thanks, Chris ... View more

Hi Mary - sorry, I missed your July response. I double-checked the behavior - it seems to be working as expected after the June release (both feature and field definitions are honored when exported by owner / admin) so there might be something specific going on with your layer. I'm happy to take a look but would need access to the layer as owner (feel free to email me at cwhitmore@esri.com, if this is ok). Otherwise, it's probably best to contact support again and work with them to troubleshoot via screenshare, etc. Thanks, Chris ... View more

Hi Rob, Could it be an HTTP / HTTPS issue? The WFS is defined as HTTP (and doesn't appear to support HTTPS). If it's expected that HTTPS isn't working and you must use HTTP, the browser would need to use HTTP to load the layer. I tried the same steps and seemed to get the prompt for authentication (when using HTTP): Thanks, Chris ... View more

Sam Perkins ok great good to hear. The Ms and Zs change makes sense (when they are present, geometries are processed a bit differently in some cases. It looks like in this case, this resulted in null geometry for a few features). Adrian's suggestion should have worked as well - when running the repair geometry tool, make sure OGC is selected as the validation method.  If you're able and willing, it'd be great to contact support with this case and get an issue logged that we can look into further. Here is support's info: https://support.esri.com/en/contact-tech-support.  thanks, Chris ... View more

Great thanks! Sorry should have also asked - which features are you seeing that aren't displaying. ... View more

Hi Sam, Is it possible to share the layer? Thanks, Chris ... View more