Latest Contributions by MachielVan

I often see ArcGIS Online abbreviated in one of two manners: either "AGO" or "AGOL". Is there any "official" way to write it in short hand? "AGO" makes much more sense to me since "Online" is a single word, but I guess using "G" for "GIS" throws this logic out the window.  ... View more

Hello All,  I'm seeking confirmation regarding the post-retirement availability of the ArcGIS Collector application via the iOS and Android mobile app stores. I recently submitted Esri Support Case #02938167 for a determination on this question. See the attached screenshot of the case resolution:  As you can see, the support representative clearly indicates that the application will no longer be available for download from the mobile app stores post-retirement. However, I found conflicting information provided by Esri Contributer Jeff Shaner in the following posts:  https://community.esri.com/t5/mobile-gis-questions/taking-away-explorer-collector-option-for-ios-12/m-p/811073 https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/whats-new-in-arcgis-field-maps-september-2021/ I am wondering if anyone has a definite answer to this question and can provide documentation, as this may have broad implications for a variety of Esri customers.  Thanks! ... View more

A helpful tip for enforcing Required Fields when publishing Feature Services to ArcGIS Online: For any Feature Layers that uses fields that do not allow null values ("Required Fields") and do not also use a list of coded domain values, it's important to know that you must reset the default values in the feature template of the Feature Layer to null in order for the fields to actually require a user-input response. This can be achieved by the Item's owner by entering the administrative mode in the REST directory (typing "admin" between the "rest/" and "/services" portions of the URL, selecting "Update Definition". You can search for the portions of the code that contains "templates", then reset the default spaces, zeroes and dates to "null". This must be executed prior to any records being entered into the data table. If you neglect this step, you'll notice that the feature templates will contain a zero value for any integer or double fields, a space for any string fields, and a default dateTime for any dateTime fields.  ... View more

Description: Instead of publishing a feature layer along with the web form of a Survey123 Survey via Survey123 Connect, set the Survey to submit results to an existing table. The hosted table can be related to a feature layer that can be included in web maps used in the ArcGIS Collector or ArcGIS Field Maps applications. This setup allows users to view Survey results in the popup of the related feature in the ArcGIS Collector or ArcGIS Field Maps application, which is an extremely useful feature when providing mapping services for inspection projects.  Steps: Design a Survey via Survey123 Connect. Design a geodatabase table via ArcGIS Pro or ArcMap that matches the schema of the Survey output. Design a feature class for use in ArcGIS Collector or ArcGIS Field Maps via ArcGIS Pro or ArcMap. Make sure the feature class includes a field that stores unique ID values that is also included in the geodatabase table schema. Create a relationship class that passes a Primary Key value from the unique ID field in the feature class to the equivalent, shared field in the geodatabase table (set as the Foreign Key). Publish the feature class, geodatabase table, and relationship class to ArcGIS Online. Open the XLSForm for the Survey via Survey123 Connect. Set the value of the form_id column to the name of the published hosted table, and set the value of the submission_url column to the REST URL of the table (the REST URL can be obtained via the lower left corner of the table's Item page in ArcGIS Online). Publish the Survey to ArcGIS Online. TEST! ... View more

I published a survey to my organization's ArcGIS Online portal, then configured a custom popup in an associated web map to launch the survey from the popup of a polygon feature class.    At first, I used the ItemID supplied by the REST endpoint, but that caused an "Unpacking Error" in the field app at first, then it failed to find the survey and returned a message regarding the ItemID being unknown.    When I checked the Survey123 webapp Collaborate section for the auto-generated Share url, I noticed the ItemID associated with the survey was completely different from the one supplied by the REST endpoint. Is this normal?    The good thing about this dynamic is that the share url seems to remain constant even if the survey is deleted and republished, so the launch-from-popup functionality is preserved.    I just think it's odd that the ItemID in the share url differs from the REST endpoint, and if that's the case, how are the two ID's related??   -MV ... View more