Select to view content in your preferred language

Feature service editing capabilities not honored in map viewer and Experience Viewer

680
3
10-29-2024 08:30 AM
EdwardMcFarlin
Occasional Contributor

My organization recently upgraded to ArcGIS Enterprise 11.3 from 11.2 and I am experiencing some issues with editing features within Map Viewer and Experience Builder that were not present before the upgrade. I have a feature service that is referencing registered data from a SQL Server enterprise geodatabase. The feature service is enabled for editing and users are allowed to add and update features, but not delete them.

FeatureServiceSettings.JPG

 

Additionally, in the edit widget settings for the Experience, the delete features is disabled (and can't be toggled on).

EBSettings.JPG

 

But the form still allows the user to delete features. I also tested this with other users that are not admins and they are able to delete features as well.

Delete.JPG

 

Additionally, this warning appears at the top of the form in the Experience: "Editing is disabled but you have privileges to edit this layer". This warning appears for the other users I asked to test this as well.

Perms.JPG

 

Strangely, there a few layers in this feature service that are in this Experience where deleting is disabled, and the privileges warning does not show up.

Deleting features from this same feature service seems to be disabled when editing in map viewer classic and Field Maps.

3 Replies
IngridHogle
Frequent Contributor

@EdwardMcFarlin , did you ever resolve this? We just upgraded to 11.3 and I am seeing the same issues.

0 Kudos
lah
by
Frequent Contributor

Same. Extremely disappointing as we are needing to migrate our WABs and Experience Builder is still this bad. 

The settings for my feature are set to allow attribute updates only. Yet, somehow, ExB still allows users to create new, update geometry, AND delete features. (11.3 - SQL non-hosted feature service)

lah_0-1735834114488.png

lah_3-1735834285951.png

 

0 Kudos
IngridHogle
Frequent Contributor

I was able to work with Esri Support to get this resolved. We had a custom member role that had Updates allowed under Administrative Privileges. Toggling this off fixed the problem. (Note: Members with the Administrator Role can still edit all hosted layers (and referenced layers, it appears), regardless of whether those layers were shared as editable feature services.)

0 Kudos