Latest Contributions by JohnFannon

Currently ArcGIS Field Maps can be opened using a set of pre-defined URL parameters (see https://doc.arcgis.com/en/field-maps/latest/prepare-maps/deploy-your-map.htm). These are ok for some basic workflows, such as creating a specific feature in a predfined layer. However, we have customers in the utility sector (also applies to others too) that use work management apps (e.g. Salesforce, SAP etc) that would like to integrate with Field Maps using URL links in a more general way. For example, one workflow might be to launch Field Maps at a specific work order location and then allow the user to collect multiple different features which are then all linked to that work order. This type of workflow is currently very difficult to acheive in Field Maps with the available URL parameters and Arcade (e.g. the work order information must be passed in as attributes of a specific feature). I would like to proposed that a customParameters parameter is added to the Field Maps URL schema. This could be a json string representing a dictionary of objects. For example: {myParam1: "Some text", myParam2: 123} These custom parameters could then be made available in Arcade through a function (e.g. GetCustomParameters) and therefore used within forms, field calculations, popups etc. This would allow passing in generic custom parameters into Field Maps from other apps and use of them within Arcade, either for populating attributes (e.g. work order number etc) or in logic within forms (e.g. if job type is x then enable certain fields within a form). Adding this functionality would improve and extend the integration possibilities for Field Maps and help customers acheive more advanced workflows in the field. ... View more

We have recently noticed that ArcGIS Field Maps does not display any copyright attribution/credits notice alongside the map or anywhere within the app (see below).   The Markup > Share screenshot option also produces a map image that does not include copyright attribution/credits (see below).   This appears to be contradictory most other ArcGIS apps (including Pro and web apps) where copyright attribution/credits is displayed, either as text or as an clickable/expandable area (see below for examples). ArcGIS Pro: ArcGIS Pro    ArcGIS Web App (Instant App): ArcGIS Web App (Instant App)   Whilst I understand there is limited space within a mobile app, almost all data (even free/open data) requires display of copyright attribution/credits alongside the map as part of the license terms/terms of use, including data within Esri and other third-party basemaps. Technically, using such data within ArcGIS Field Maps may currently be breaching copyright/licensing terms, because no such attribution is displayed or available. The suggestion is to provide a clickable/expandable button within the map area in Field Maps, which displays attribution from all layers in the map (including basemap and operational layers). This should work in a similar way to ArcGIS Pro. This is very important for most organisations/customers/partners, who may not be able to deliver solutions using Field Maps due to the licensing requirements of their data providers. ... View more

I would like to suggest a "Lock Editing" option similar to the "Delete prevention" option on ArcGIS Online items. This is to prevent accidental modification of the item (e.g. web map, web app) by others in the organisation that have the correct permissions. For example, we have several web apps and associated web maps that are used as live applications by others in the organisation. However, it is relatively easy for someone with the correct permissions to open the item (especially web maps in Map Viewer) and accidentally edit and then save. This change then affects the live application(s). Having a "Lock Editing" option on the item, would prevent a user (even with the correct permissions) from editing the item and saving, without first disabling the "Lock Editing" option. This would work in a similar way to "Delete Prevention", forcing the user to make a concious decision to edit the item. For example:   Note that this is separate from turning on/off editing of feature layers. This is to prevent editing of the ArcGIS Online item itself and is probably most applicable to web maps and apps, but could equally be applied to item details/metadata of feature layers and/or editing of feature layer views etc.   ... View more