Latest Contributions by DataOfficer

I've just tested out one of the new Instant Apps to create an app using the Interactive Legend template. All works fine until I press the Publish button, at which point it hangs indefinitely (spinning blue circle). Unable to close the 'Publish' window or cancel. Google Chrome Version 91.0.4472.124 (Official Build) (64-bit). Closing the browser window and accessing my ArcGIS Online Content I can see the app in the Content list, but opening it shows the default template (Interactive Legend Sample: Global Power Plants) rather than my customised app.   ... View more

As of the May update, a 'more info' side panel appears by default when apps are opened in ArcGIS Hub. For many users this information is unnecessary, and takes up valuable real estate on the page. Either hiding this by default, or having an option to hide this would be preferred, rather than the user having to hide it each time. Inspiration taken from this post: https://community.esri.com/t5/arcgis-online-questions/minimize-more-info-side-panel-of-arcgis-hub-by-default/td-p/1067627 by @BenjaminSkinner.   In our use case, our community users are opening maps, dashboards and other apps from hub pages, and are only interested in seeing the map etc. They have no interest in the additional details. ... View more

We are noticing some peculiar behaviour with some of our hosted views. Is anyone else experiencing the same? Background: We use hosted view layers to share in webmaps with some of our community (Hub) users for surveys.  Process: Hosted view layers are created from the feature layer, using the View Definition to control what is shared in the layer. Editing is not enabled on the hosted view. The data appears present and correct when viewed from an organisational admin account. The hosted view layers are shared to the community users via groups.  Issue: The community users see (or rather don't see) an empty/blank layer (no rows in the attribute table and no geometry on the maps). Workaround: As a temporary solution, we have found that if we turn editing on in the Settings of the view layer, save the Settings, then turn editing back off again (and save), the view layer appears as expected. Any ideas what may be causing the view not to be shown to the user in the first place? ... View more

Our users are experiencing issues with the geoshape tool in Survey123. We have multiple surveys (all built in Connect) that use geoshape questions. The method is set to vertex.  When users draw a polygon on the map interface, they experience the following issues when using the windows desktop field app (tested in versions 3.12.274 and 3.12.277) (but the same issues are also seen when testing in Connect 3.12.232): If moving the map, the polygon moves out of sync with the basemap (rather than being fixed to the basemap it 'floats') If saving their polygon drawing (by clicking the tick button), the polygon shown in the form is in the wrong place (e.g., moving southwest of the correct position). After submission, when the polygons are shown either in an ArcGIS Online webmap, or in ArcGIS Pro, polygons can appear in the wrong locations (as described above), and may appear bigger or smaller than the area traced against the basemap. Despite this, the area calculations appear to be correct based on testing so far (i.e., an area calculation in the form matches the area of the submitted polygon shown in ArcGIS Pro).  These issues appear to occur regardless of basemap. Is this a known bug? Examples below: Fig 1. Original polygon drawing Original geoshape drawing Fig 2. Polygon has 'drifted' Polygon has moved (in map/drawing mode) Fig. 3. Polygon has drifted (shown in form view) Polygon has moved (in form view) Software details: Tested on a laptop running Windows 10 with version 3.12.274 of the x64 Survey123 Field App, and again with version 3.12.277 of the x64 install. Another colleague has also tested with 3.12.277 and has the same issues. Also tested on a Samsung A71 running Android 11 and version 3.12.277 of the Survey123 Field App. - doesn't appear to have the same issues. Possibly limited to the x64 version of the app? ... View more

We are often creating hosted views which are highly similar, but tailored for different user groups. Currently, we have to create each view separately from scratch off of the hosted feature layer. This takes a lot of time as we have to set each of the features, fields and extent in the view definition each time. It would save a lot of time if it was possible to clone or duplicate an existing hosted view whilst still maintaining its connection to the hosted feature layer. We could then make minor modifications to the cloned views (e.g., defining different extents). It is currently possible to save hosted feature layers as new layers, but these are independent from the hosted feature they were created from and so do not meet our needs. ... View more