Latest Contributions by SFM_WillBrewer

I'd like to make a custom domain (pick-list) for a feature service that is a view. Will this corrupt the parent service? ... View more

We have recently (since March AGOL update) noticed an issue with edits synced from offline maps in Collector. The edits sync successfully but do not appear in hosted feature service views. The primary feature service (from which the view is made) does see them, but they do not trickle down to the view. ONLY after an edit is made to the view through an online map in Collector or AGOL web map does the view update with the edits synced from the offline map. This is a major problem because any views we share with partners do not contain all the data. This jeopardizes our workflow with Collector and AGOL entirely. Miaogeng Zhang Xander Bakker Kelly Gerrow's Blog Collector‌ AGOL Example (part 1) - Two points exist in the database which were synced at different times from an offline map. Only one (left) is visible, while I can still select them both in the map and the attribute table shows two selected while only one is visible. Example (part 2) - If I scroll in the other 'ghost' point becomes visible in the map, map but does still does nt appear in the attribute table even though it says 2 are selected. Example (part 3) - BUT when I add a record with the web map editor or Collector online, the view updates properly. All the records draw and the attribute table is correct. Below the red point was added through the edit tool and now all points are visible and 3 features are in the attribute table which is correct. ... View more

The new capability within Collector to Edit Multiple is a incredibly powerful functionality. It has many great applications, but we are concerned that allowing any user with access to the map and the correct edit privileges to mass edit features can create problems. Is there a way to limit this in Collector, the map or the service in AGOL? Due to constraints in our program we must allow users to edit all features so it is conceivable that a user with 'fat fingers' or malicious intent could select and update thousands of records at once. We do want the reuse field entries capability in the 20.1.0 Collector release, but how do we at least turn off the edit multiple?Jeff Shaner ... View more

In earlier iterations of the Dashboard, Layer Actions could be configured in the map to either filter, flash, pan, or zoom to a feature(s) of a layer that is acted upon by another filter (category/number/date selector). This functionality has changed to where these layer actions (filter, flash, etc.) only work when the feature(s) is selected in the map with the new select tool. In my opinion, it was far more useful to zoom to, flash, etc. to a feature that was selected from the larger category filters hosted on the top or left side of the Dashboard. Can these functionality be returned or make it more clear where the setting can be adjusted to either A) Use Selector Filters to act upon the map or B) Use Select Tool? My Dashboards built 2-3 years ago no longer work as expected because of this change.   ... View more

Creating a view with the Python API does not honor the settings of an existing hosted feature service that are preserved in the JSON. Settings configured in the Visualization tab in ArcGIS Online for field values like "visible": true/false and general layer info like "popupinfo" that are configured in an existing service do not carry down to views that are created with the ".manager.create_view" module in the Python API. These settings ARE carried through when the view is created manually in ArcGIS Online. Above Left - Original Settings in Service                 Above Right - Altered settings circled after view is made with the API. ... View more

Access to fields and domains has improved in ArcGIS Pro. However, one key function is still missing and some functionality was not carried over from ArcMap. 1. Loss of functionality - Pro automatically alphabetizes the domain list based on the domain code without warning after a code is added and the domain/field window closed out. It did not do this in ArcMap.                   GOOD - Original Domain Order                 New Value Added                 BAD - Realphabatized Domain Order       Ex -     This is undesirable because we want a specific domain order that puts the most highly used domain values higher on the pick list for an application like Collector. We do not want to use a 1,2,3,4 etc. coding system for domains because AGOL and ESRI products in general do a poor job allowing export domain descriptions instead of domain codes. We want to share a feature service from AGOL with partners and have allow to them to export a legible (excel, shp) dataset. 2. Missing Functionality - Why can we not manually reorder domain coded values in Pro? The 'Sort Coded Value Domain' tool needs more functionality besides just sort by ascending/descending. In the ESRI ecosystem the only way to do this is in AGOL. It should belong in Pro too. ... View more