Latest Contributions by ScottPrindle

Hello Nathan Enge, Thank you for submitting this idea! How are you currently addressing this issue in your workflows? Others, When voting for this idea, please consider leaving a comment to share your perspective. How would this improve or update your existing workflows? Thanks, Scott ... View more

Hello Simon Morgan, Thank you for submitting this idea! Since it looks like your request is built around data collection within Collector for ArcGIS, I've removed the other app categories. However, if there are specific use cases or workflows you can outline where the Apple Watch would be useful with another app, please don't hesitate to update this idea with a comment or additional information! Thanks, Scott ... View more

Hello mark crow, Thank you for submitting this idea! I've removed a few of the categories, since this request appears to be for reporting functionality in ArcGIS  similar to what is currently available in Survey123. If there are functional requests for any of the apps, please feel free to correct me. When considering this request, what kind of data do you have in mind? How is it being collected or generated? How would you like to report on it? How are you currently accomplishing your reporting? Any expansion of your use case will be beneficial in helping us understand your workflows and needs. Thanks, Scott ... View more

When supporting this idea, please consider checking out the Collector Aurora Project. Aurora is currently in beta on iOS, and there are a number of updates to the user interface which could improve your workflows. ... View more

When voting for this idea, please consider leaving a comment sharing your perspective or additional thoughts. Also, consider checking out the Collector Aurora Project. The user interface is being given an overhaul, and any feedback you have related to this idea would be greatly appreciated! ... View more

Hi Kieran Smith, Thanks for submitting this idea and expanding on it in the comments! In order to ensure support is clearly associated with one suggestion or the other, could you submit a separate idea for your second request? Everyone else, When voting for this idea, please consider adding a comment to share your use case. How would this change improve or affect your current (or planned) workflows? Are 4 rings adequate for your projects, or would you need 5 or more? If more, why? Any additional information you can provide in the comments will help our development teams create the new functionality with your needs in mind. Thanks, Scott ... View more

When voting on this idea, please consider sharing any trends or other information you would like to be able to pull from historic data. Thanks! ... View more

Hello jay kapalczynski, The issue outlined in the original post was the bug I linked in my previous comment. The patch is for 10.5 specifically, while the fix was rolled into 10.5.1. If you are seeing this specific issue, where you've published your feature service as a user that is not the data owner, and you get a 500 error, there may be something else going on. A 500 error is pretty generic, but essentially means the failure occurred on the server side. If you are encountering a 500 error with sync, and you do not have the same data owner/publisher mismatch as stated elsewhere in the comments, then there is likely something else going on. Have you been able to contact Esri Support about the issue? Could you provide a bit more information here about your data model, your workflows, and the situation leading up to any 500 errors you see? Thanks, Scott ... View more

The root cause of this issue is touched on in a few comments. Joe Hershmanshared the relevant patch for the original issue outlined by OP. The issue is tied to the database connection file's credentials that were used when publishing the service. More specifically, if the data owner (ex. GISADMIN) differs from the service's publishing credentials (ex. Publisher, GIS, etc.), at 10.5 the sync would fail. If this is the issue you're encountering, then the patch should be applied to your environment, or upgrade to the most recent release (if possible). If these options don't work, you can attempt to republish your feature services using the data owner (ex. GISADMIN). This is a workaround, so it should only be done if there are no concerns with this approach. The bug (BUG-000103326) can be viewed here. Thanks, Scott ... View more

Tom Crowther's presentation about biodiversity and how we approach climate change was great! Here's the NASA video included in his slides, visualizing CO2 emissions during 2006. This sort of visualization can help make sense of an abstract but important topic. We can't always see the stuff around us (that distribution of nematodes!), but we can use multitudes of data to draw conclusions, or develop new data for analysis. ... View more

Craig Gillgrassshared some powerful developments coming to Esri's apps with regards to location tracking. Alongside Craig were Madeline Schueren and Adrien Meriauxdemoing ArcGIS Indoors and virtual/augmented reality with the ArcGIS Runtime. These native apps can fill some new needs for you, but please head over to ArcGIS Ideas‌ to share your thoughts on how you envision using these apps, or how you would improve them! ... View more

Cobb County's use of Esri apps is powerful! Their use of Operations Dashboard and a few custom mobile apps (Cobb Commute) show how the county is sharing useful traffic information, as well as current cameras! ... View more

In case you missed it: J.D. Irving included an embedded survey from Survey123 for ArcGIS as an embedded dashboard element! ... View more

Hey Thomas, I don't see any references to archiving or versioning in the link you shared. However, there is a related link here, which is listed on that page. This outlines some of the different approaches to preparing your data for offline use, whether that's with versioning or archiving. There may be multiple ways to get to the same result, but we certainly want to figure out what's happening with your offline edits in the current workflow. It's also possible that something is amiss in the data model or the workflow in Pro. I would definitely encourage a support case to get an analyst's assistance in troubleshooting the issue. If you are seeing essentially the same behavior between versioning and archiving (the offline map is successfully created, but edits that are synced do not appear in the enterprise geodatabase), then the problem doesn't lie with those settings specifically, but perhaps somewhere else (data model, DBMS permissions, web map permissions, Pro functionality, etc). Sync is a pretty complex process, and it is still pretty new to Pro, as you noted previously. There are database replication topics, ArcGIS Server/web server topics, ArcGIS Pro client workflows, etc. All of these things overlap and really muddy the waters when something goes wrong, so I think it's important to identify and isolate every variable at play. Please feel free to PM me if you have any questions or issues with the case you create with us! As more is discovered about the sync issues you're encountering, keep us posted in this thread. Thanks, Scott ... View more

Hello Adrien Roth, The reason I shared these links is because we should first be approaching these versions and their cleanup from the client that created them, in this case ArcGIS Server. The REST API provides some tools to unregister a replica, which has created and managed all of the SYNC_SEND, etc. versions. Before going to arcpy.da.ListReplicas or directly to the DBMS, these should be investigated at REST first. Unregistering the replica at REST will normally clean up all of those dependent child versions, but it will also leave the initial child "Esri_Anonymous_service_###########" (in case there are edits that have not been rec/posted back to the parent version). If everything has been done properly through ArcGIS Server and the REST API, but orphaned SYNC_SEND or other versions still exist, then there is likely an issue that Esri technical support should be made aware of. As long as the replica remains in the replicas resource, then those child versions should remain as well. Additionally, whenever something appears to have gone wrong with sync, consider temporarily bumping your ArcGIS Server logs up to DEBUG level and reproduce the failure or behavior that appears to orphan versions. The service with relevant messaging will usually be the SyncTools GP service. These logs collect a lot of information, so it should only be done when necessary. However, these logs can be extremely useful when you contact Esri technical support about sync issues. Thanks, Scott ... View more