idea While editing in Map Viewer in AGOL limit fields - equivalency with map viewer classic in ArcGIS Online Ideas

While editing in Map Viewer in AGOL limit fields - equivalency with map viewer classic

JohannaKraus2 — Thu, 14 Sep 2023 20:19:20 GMT

In Map Viewer Classic the viewable fields in the pop up are the ONLY viewable fields when users edit the data. In Map Viewer the user gets ALL the fields when they edit the data - this is unnecessary and cumbersome for the user.

In appears that in in classic the viewable fields in an edit session are based on the pop-up, this does not appear to be the case in Map Viewer so we need another way to limit the fields available to the users while they are editing.

Re: While editing in Map Viewer in AGOL limit fields - equivalency with map viewer classic

JörgMoosmeier — Fri, 15 Sep 2023 07:20:37 GMT

In MapViewer you can limit the visibility of fields or the editable fields via Smart Forms

Re: While editing in Map Viewer in AGOL limit fields - equivalency with map viewer classic - Status changed to: Already Offered

AlixVezina — Fri, 15 Sep 2023 16:21:24 GMT

@JohannaKraus2,

As @JörgMoosmeiermentioned, if your map contains feature layers (hosted feature layers, hosted feature layer views, hosted table layers, subtype group layers, or ArcGIS Server feature layers), you can define forms that editors can use when they update field values for the feature layers in the web map. This also allows you to customize which fields are visible and editable.

Re: While editing in Map Viewer in AGOL limit fields - equivalency with map viewer classic

James_Whitacre_PGC — Wed, 07 Feb 2024 23:47:29 GMT

I believe that listing this idea's status at Already Offered is an error and incorrect. The functionality that @JohannaKraus2 is asking for is NOT fully implemented as it was in the Map Viewer Classic as the title suggests. While in the description @JohannaKraus2 is really only concerned with editable data, this is not implemented for non-editable data. For example, as of right now there does not appear to be a way to restrict fields for Joined View Layers, which require all fields to be included from both joined datasets. Also, if export is allowed, you cannot restrict what fields are exported. Therefore, I think this idea should be reclassified as Partially Implemented (or equivalent). Being able to restrict the fields of non-editable layers and table and for joined views is important for data security and quality.