Latest Contributions by PaigeLester1

Similar to the Update (Append) button functionality for hosted features services, add a Truncate button! ... View more

For disconnected use with Collector, a side-loaded .tpk basemap is somehow unavailable in my map? I have verified that the basemap is on my local device. It worked fine before the update. Was this capability broken with the new update? ... View more

In any of ArcGIS Online's web maps and applications that provide editing, such as Collector and Web App Builder, it would be nice to be able to restrict editing to specified scale levels per feature layer. For example, I want users to see data at small scales, but I don't want them creating or editing data at small scales. I want to be able to specify the scale level at which point the user can begin editing the feature layer.  The workaround I am using is to create a view without edit permissions that appears at those smaller scales, while making sure the editable parent layer is only visible at the specified maximum scale I prefer for editing to take place. So, this works, but it adds extra complexity that I wish I didn't have to maintain.  ... View more

In any of ArcGIS Online's web maps and applications that provide editing, such as Collector and Web App Builder, it would be nice to be able to restrict editing to specified scale levels per feature layer. For example, I want users to see data at small scales, but I don't want them creating or editing data at small scales. I want to be able to specify the scale level at which point the user can begin editing the feature layer.  The workaround I am using is to create a view without edit permissions that appears at those smaller scales, while making sure the editable parent layer is only visible at the specified maximum scale I prefer for editing to take place. So, this works, but it adds extra complexity that I wish I didn't have to maintain.  ... View more

In any of ArcGIS Online's web maps and applications that provide editing, such as Collector and Web App Builder, it would be nice to be able to restrict editing to specified scale levels per feature layer. For example, I want users to see data at small scales, but I don't want them creating or editing data at small scales. I want to be able to specify the scale level at which point the user can begin editing the feature layer.  The workaround I am using is to create a view without edit permissions that appears at those smaller scales, while making sure the editable parent layer is only visible at the specified maximum scale I prefer for editing to take place. So, this works, but it adds extra complexity that I wish I didn't have to maintain.  ... View more

I can't get any offline maps to download on any of my Collector maps on either version of Collector. Anyone experiencing this?  ... View more

Using the new Collector app on several different iPads and iPhones, newly added points disappear from the map. When switching immediately back to Collector Classic, the point is there. So, it seems the data is safe, but this certainly makes the new Collector unusable until this is resolved. Anyone else experiencing this issue? ... View more

Anyone seen this error message before? I was trying to overwrite a hosted feature layer on ArcGIS . The feature layer is not editable, but is sync-enabled. Any help would be appreciated.  ... View more

I want to deploy teams using Collector for Windows on Surface Pro 2 tablets for field surveys. Instead of using a new, empty feature layer, my editable feature layer is one with existing point data and attributes. I have it set to only allow the field editor to toggle specific fields - they cannot delete existing or add new points. I am using subtypes and coded value domains. I am using Collector version 18.0.1.0. Note:  All three of the listed issues below affect Collector for Windows (using a Surface Pro 2 tablet), yet #3 also affects Collector for iOS (iPad Pro/iPhone 6s). Collector for Windows does not recognize certain layer symbology or specifications set forth in the web map and its hosted feature layers as it does successfully in iOS. For example, I want my editable feature layer to reflect no symbology when its points haven’t been changed from their initial status. In the Windows application, on both desktop and the Surface Pro 2 tablet, all points have a red dot symbol instead. Another issue in Collector for Windows is that the app is allowing pop-ups for features that I have purposely set to not show up. Collector, for both Windows and iOS, is recognizing some, but not all subtype default values. For example, when choosing either “Major” or “Destroyed”, the HABITABLE field should default to “0 - NO”. This works as designed in ArcMap, but not in Collector for either platform. Issues 1 and 2 are more damning than #3. This must be a bug - has anyone else experienced this? Perhaps Esri could get their Windows team to take a look before we get slammed with hurricanes this season?  ... View more

 I am using Collector version 10.4.2 with iOS devices including both iPhone and iPad. My editable feature service is hosted on ArcGIS Online, along with a few other non-editable layers present in the web map. My editable feature service was a point feature class shared from a file geodatabase using ArcMap 10.3.1, and includes subtypes and various domains. We are also using our own tile basemaps. The task was to send staff out to survey different geographic areas where they would collect 27 – 28 points each, and take four (4) photos at each point. This operation was conducted disconnected by four different groups simultaneously. Once back in the office, connected to Wi-Fi, the offline syncs successfully uploaded the points, but the attachments failed. Over two days, using different Wi-Fi connections, and even instructing them to collect less information at a time between syncs still proved to fail to retain the photo attachments. Is there a limit to the file size for the offline sync upload for photo attachments with the Collector app? What is the limit? Once the sync fails, where have my photos gone? Are they retrievable at that point (able to still be uploaded and attached to their point data), or do I have one chance at success or they are lost forever?  A workaround that I attempted was to instruct staff to save each photo to the device after each submission, which is time-consuming and averts from using the Collector app as designed. However, the photo metadata is stripped with this method, so this option is useless. Either Collector is going to be a reliable data collection method or it’s going to be a toy with no use or real value. Which is it, ESRI? Please advise. ... View more