Latest Contributions by JeffGarland_AGOL

Thanks for the reply.  To extend the initial question a bit further.  Is the design intent to be able to access a geodatabase hosted on Azure SQL DB with an on premised ArcGIS Desktop client? Reading through the documentation for ArcGIS Server hosted on AWS it is quite clear that the geodatabase needs to replicated from on premise to the cloud.  Will that be the case for Azure SQL DB or can one create a hybrid scenario as described above (production geodatabase in Azure SQL with access and management by on premise ArcGIS Deskop client)? ... View more

Interestingly I can attest to both cases above.  I updated to Office 2016 on a Win 8.1 box that previously had  Office 2013.  I could get the Esri map add-in to install. I just tried it on a new Win 10 box with a fresh install of Office 2016.  Failed to install.  To test, I then uninstalled the Office 2016 version, installed the Office 2013 version and then installed the Esri map add-in.  After that I then installed the Office 2016 version on top of (I didn't uninstall) Office 2013 version. The Esri map add-in was enabled and functional. If it matters, both of these were the 64 bit version of Office. ... View more

John: I came across your posting because I was under the impression that the search widget didn't support entering in a coordinate pair as you state in item number 6 in your post.  Nothing about the configuration of the widget would indicated that, but if you do enter in a coordinate pair of the coordinate system displayed in the app it will find and provide the ability to zoom to the result. Note that Robert provides a nice enhanced locator widget that provides a lot of options, but my customer use case is hosting WAB on AGOL and thus no custom widgets.  There is a posting titled "Web AppBuilder Search/Geocoder widget" on ideas.esri.com if you're interested. ... View more

Can I add to this list the ability to control what coordinate system for entering in a coordinate pair to search on.  Not sure to start another idea or if you could add to this one.  The enhanced locate widget that Robert S. provides would be a good template. ... View more

Thanks again.  I was searching on AGOL with your user name.  It's a mystery to me where Esri keeps squirreling away user generated content.  I guess I'll start searching GeoNet.  ... View more

Robert.  Thanks for your help.  I migrated from the 3.0 Flexviewer to 3.7.  I'm inheriting the project from someone else and it obviously hasn't been updated in a couple of years.  I understand you're on to the WAB. Is there a buffer widget equivalent?  Searching AGOL I'm not finding anything short of the land use app.  Alternative is to build a quick app ... View more

Robert: XML file is attached.  I would have thought I wouldn't have had to update the XML file with the upgrade to 3.7.  The buffer was working in the previous version. Thanks for taking a look at this. ... View more

I'll chime in with a similar observation.  I think one has to make the distinction between geometry types and also the complexity of the feature (e.g. number of vertices).   I ran into this problem when using a custom location type where parcels where the location feature.  Things worked relatively well until we went from a couple of hundred to a couple of thousand.  In short, the map becomes unusable. All of this was done 32 bit Excel 2010 with the ESRI map add-in version 2.1.0.143 and hardware acceleration enabled. I then tried an custom location type using PLSS sections (used the BLMs unique ID).  Still polygons but much simpler.  I could get up to about 5,000 and it start puking.  I could still filter for a smaller subset (a couple of hundred) and then performance would improve.  TO determine if it was somehow the server providing the custom location type, I create a spreadsheet of all the zip codes in the US (approximately 33,000 plus) and ran against the ESRI provided zip code location type.   If I started with a filtered data set and the result set being below a thousand things worked fine.  Once I started filtering to anything above 2,000 performance took a hit.  (Interestingly, the locator would return errors on the zip codes.  I downloaded the data from the census.  Not sure it they have erroneous zip codes or if ESRI locator is incomplete.)  Once I got to the point where there were too many records I couldn't recover.  I could remove the table from the TOC, filter to a smaller number, add the table back to the map, but it was locked up. In summary, the add-in works great on points, but breaks down pretty quickly when you work with polygons.  I suppose you could write an Excel macro limiting the number of records that can be filtered and displayed in Excel, but that seems a bit convoluted.  Too bad, I really like the concept and the folks at my company love being able to visualize their data on the fly. Migrating to 64 bit Excel isn't a solution, because just about every other add-in in the world ( and we utilize quite a few) are still in the 32 bit world. ... View more