Map Level Attribute Editing Control in Map Viewer

[James_Kellough]

I'm looking for help or advice on functional differences over attribute editing control between the Classic Map Viewer and the New Map Viewer.

In the Classic Map Viewer, popup control was a one stop shop, users had control of field visibility, alias names and editing. Specifically, users where able to have independent control over which attribute fields were editable in Feature Layers (see attached screenshots). That level of control appears to be gone from the New Map Viewer. Popup control has been broken out into separate popup and field management panels and neither appear to offer any editing control. Now it appears control of attribute editing is all or nothing - all fields are editable or no fields at all are editable.

Is field editing control available at the web map level in the New Map Viewer?

I'm aware that field level editing control is available at the widget level when maps saved with the New Map Viewer are used in the Edit Widget within an ExB app. This is not an appropriate or even available option for my use case. I am using the legacy Crowdsource Reporter/Manager apps. I won't go into specifics here but basically the data submission form is automatically populated by reading all available fields for editing. In many case admins don't want all fields available for editing or even viewing for that matter. New Map Viewer appears to have taken that field level control away from map authors making it an incompatible option for use with the Crowdsource Report/Manager apps.

For the time being, I can continue using the Classic Map Viewer while it still exists to work around this issue unless I'm simply missing something in New Map Viewer. Any thoughts or suggestions? If this is indeed a functional deficiency in New Map Viewer, I will submit a request for its inclusion with ArcGIS Ideas.

Cheers.

[EmilyGeo]

Hi @James_Kellough, 

Have you tried using forms in Map Viewer?

When you create a form, you can choose which fields to display on the form and then configure properties including whether to make them editable or not.

Here is a link to an article on getting started with forms in Map Viewer: https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/smart-forms-arent-just-for-field-map...

[James_Kellough]

Thanks, I will look into this and report back.

[James_Kellough]

Hi @EmilyGeo,

Thanks for the suggestion to use forms in the New Map Viewer, unfortunately it did not work. Perhaps this web map feature, like some others, only works in ExB and not legacy apps? I've included screen shots of the web map popup, fields and form panels configuration as well as the Crowdsource Reporter App data submission form showing the fields that I excluded in the web map form. I guess I'll stick with using Classic Map Viewer for use with this legacy app for the time being.

I know ESRI has released in Beta a new Manager Instant App to replace the Crowdsource Manager app but there is no indication of a suitable replacement Reporter app with equivalent features and functionality, do you know who or where I can make recommendations to either maintain the existing app or ensure equal functionality in any future replacement app?

Popup Panel

Fields Panel

Form Configuration

Crowdsource Reporter App Data Submission Form

[James_Kellough · Accepted solution]

Based on research, help from the community and a lot of trial and error the simple answer to this post as worded is yes, with a caveat. Field level editing control is available in the New Map Viewer but is not honoured in WAB and legacy based configurable apps.

In my particular use case, I am using a combination of new and legacy ESRI software. I was attempting to use a web map saved by the New Map Viewer in a legacy configurable app (Crowdsource Reporter). There are a number of features in New Map Viewer that do not translate or are backwards compatible in WAB and legacy configurable apps such as layer groups for instance. Forms and control over individual field display and editing capability appears to be other such features that are not backwards compatible. 

If you find yourself in a situation where you need X number of fields editable but only Y number of popup fields visible in a WAB or legacy configurable app your web map source must be saved in Classic Map Viewer. 

[EmilyGeo]

Hi @James_Kellough. 

My apologies, I didn't realize that you were working with a legacy app when I first read your question. You are correct, the legacy apps are not compatible with Map Viewer since it is build on a newer version of the JavaScript API. 

Using Map Viewer Classic, you should be able to use the pop-up configuration to specify which fields should be visible and which should be editable. Hope that helps!