Latest Contributions by ScottStopyak

Here's what I've gotten so far. Collector on Zeno 20 is officially broken because of the deprecation of TLS 1.0 and Leica's inability to update the OS because it is an open-source android fork of version 4.2. They are telling me that the ARM processor can't support an update from version 4.2. I can't find any evidence anywhere on the internet to confirm or deny that claim. Leica was looking for help from ESRI to fix it. That hasn't happened yet but Leica indicated they aren't done working with them on a fix. In a document published by ESRI about the TLS issue, they alluded to having a proxy server setup that could be configured to allow TLS 1.0 to still work. Unfortunately, they offered no instructions on how this can be done or even what specifically would or could be proxied. I don't think an entire AGO organizational account could be proxied by someone who doesn't own the domain. If you run Portal, a custom configured proxy might be an option. The whole proxy idea seems far fetched for those whose content and services are hosted on AGO and I honestly don't understand what they are talking about when suggesting this as a solution to fix Collector on the Zeno. The ESRI document Leica provided as a "solution" offers some general info about TLS but no documented path forward toward a workaround. If bought after 2015, the Zeno 20 is an extremely disappointing product. First, it came with a 3G modem that couldn't be activated because 3G is all but gone. As a non-google android fork, app selection is via Amazon Store, which has little to offer for geospatial apps. Now Collector does not work either. Leica indicates they will work on finding a fix for Collector, but it won't likely be easy or quick. There are some other gps collection apps out there that might've worked at least temporarily if the google store/services were available. The only way I can find to to make these work is with the added expense of an external Mifi and Zeno Mobile software. It's a shame because the antenna is quite good as is the construction of the unit. We got our Zeno 20 thinking we'd run it without a Mifi and with Collector (as advertised) but we cannot. The product is under warranty but we've gotten no response on whether it can be returned or exchanged for something that actually works.  ... View more

Yep. Go back to 10.5.1. I'm doing that right now, myself because 10.6.1 has been a nightmare. ... View more

This is the primary reason why we don't use AGO more, though we would really like to. There's no easy way to back things up. I've written scripts that will download data from specific hosted features but that's way too cumbersome to do for all content. The API tools to do this already exist so why is there no user-friendly front end in AGO? Also,  having backups/replication for cloud data seems like it would be a no-brainer for esri as it could potentially double the storage credit consumption with a simple checkbox added to Settings. Toggle on Backup. Set an interval. Done. ESRI doubles its money from existing users and potentially adds thousands of new customers who currently don't use it for lack of an easy backup solution. ... View more

This issue is resolved for us with the June update. Someone from another organization mentioned issues with code attachments showing up as gallery content now though. Just FYI.  ... View more

The home page comes up as it should now. I can't speak to the other issues like zooming to features since I had to rebuild my apps to get zooming working again.  ... View more

We have this issue on iOS as well. We'll try the workarounds suggested. ... View more

Our widgets were (and still are) configured to search features from site address points and parcel feature classes. Some used esri's world locator as a third option. Configured the same way, our old maps would return a result and highlight it but failed to zoom to the selection automatically or when the suggested value was clicked. When maps and apps were created anew from scratch using the same settings as the old maps, they worked again. Similarly, the permissions issues were fixed. The displayed content on the mobile version of the home page, it seems to me, is a symptom of a larger problem. The way that AGOL permissions are setup should be changed so that the underlying components of a web app don't have to be exposed in the same way that the application itself is. I shouldn't have to make the web map and services, logos, basemaps, tiles, service defs, etc. visible and searchable on their own for them to be able to be displayed in the apps. Even if all of our content was intended to be completely open (which it isn't) displaying all that content instead of selected content makes the site virtually unintelligible for it's target audience - the public. This isn't an bug ESRI should just sit on for months. It really needs to be fixed right away. You've made the GIS home page for many organizations pretty much worthless on mobile. ... View more

We're kicking around this idea ourselves. If we were going to opt out here's why: Our budget has become very tight and we need new field equipment. We aren't going to migrate ArcGIS Desktop or Server beyond 10.5.1 because we don't want to implement the necessary changes in our architecture to accommodate a redundant 10.6.x data-store. Almost no development of ArcMap or Catalog anymore as ESRI focuses on Pro. We've kept a close eye on Pro's development. It isn't ready to replace ArcMap/Catalog and at the rate they're going, it won't be for a few years after they've pulled the plug on ArcMap/Catalog. I tried in earnest to force myself to use Pro. I learned that no matter how much I wanted to like it, I couldn't. It isn't very good. It isn't stable. It does many things poorly that ArcMap & Catalog do well. At this point, I can honestly say that other than being 64 bit, in terms of overall user experience, its a step backward. Moreover, it has project-based approach that doesn't jibe with an enterprise GIS environment. It has a few cool bells and whistles but overall, its poorly implemented and not production-worthy. I feel like our maintenance money is currently being spent on Pro's development rather than the software we actually use right now. ESRI support isn't very good unless you can get routed to American support (which is quite good). That has become more difficult. It used to be, I'd tell them I had a question about ARCINFO workstation and they'd immediately route me stateside, but alas, those days are gone. I generally get better answers from the online communities. We don't have many power users who crave the latest and greatest. In fact, most our users would probably be happy if the software they use never changed. QGIS could work well for us if we don't want to re-buy licenses down the road. It's better than Pro, in my opinion, and it's free. That said, we really like AGO. We would continue to pay for AGO accounts. ... View more

Thanks, Thomas! ... View more

Let me guess. No editing of geometric networks in Pro because ESRI wants to write another half-baked, user-tested extension and charge $2500/year for it? Am I close? ... View more

Thanks! I’ll try it. ... View more

I tried to get around it by having a bat first open catalog then run my script. I had checked the sign me in automatically in the File>Sign In but for some reason it doesn't always work. There needs to be an arcpy equivalent for the tools esri is pushing out. I can easily open Pro and run Overwrite Web Layer but it's a manual process. It is unbelievable that esri is trying so hard to move everyone to hosted data but then wants me to reverse engineer tools they already have written for Pro. Is a simple arcpy.OverwriteWebLayer() too much to ask for?  Why is everything esri does half-baked nowadays? ... View more