Removing the deleting capabilities from the Edit Widget (ExB)

[KenBouchard]

Can't seem to find a way to remove the delete capabilities from the Edit Feature Widget.  I've uncheck the add record and delete record but the delete button is always there... and working!

I need to give my staff the capability to add attachment to the feature but I don't want them to be able to delete the whole feature!!  Anyone have the same issue?

Thanks,

Ken

[NateExley]

Thanks for the follow-up. I opened a ticket with Esri support, and we figured out the issue. I was not aware that users within non-shared update groups could still update and edit content. When I restructured my groups to NOT be shared update groups, the editing settings I put in the experience and web feature layer were honored - the delete option was removed from the edit window. I learned that shared update groups give members privileges similar to admins and they can update and delete the data regardless of the settings in the web feature layer or the Experience.

[HannahWilson3]

@NateExley @AlixVezina I'm having exactly the same issue, except the users are NOT part of a shared update group (sharing level is "organization")

[HannahWilson3]

@NateExley @AlixVezina I'm having exactly the same issue, except the users are NOT part of a shared update group (sharing level is "organization").

[RVRAdmin]

I second everything said here. I don't want admins to have keys to the kingdom whenever they engage with an app. In small orgs, the admins are often the only editor or one of the only data editors. And can't test true functionality as a developer with current config. Thanks.

[NateExley]

@RVRAdmin @HannahWilson3 The content I'm sharing and which I want users to be able to update some parts of, is only shared at the owner level in most cases. I learned that to remove the option to delete features but keep some editing capabilities the group needs to not be shared update, the web feature layer needs to have the "delete" option deselected from the kind of editing allowed, and the layers within the edit widget in the Experience Builder need to be/can be further tailored down to the attribute. Hope that helps your situation.