topic In Esri Enterprise Geodatabase (SQL), is it possible to give Update privileges but not Insert or Delete? in ArcGIS Enterprise Questions

In Esri Enterprise Geodatabase (SQL), is it possible to give Update privileges but not Insert or Delete?

DanielWebb — Thu, 12 Dec 2024 17:20:10 GMT

We sometimes have situations where we want to give Update privileges to someone, but we do not want them able to add or delete features. Like we just want someone to be able to edit fields but not geographic features. But in ArcGIS Pro, when I click ‘Update’ it auto-checks both ‘Insert’ and ‘Delete’. (See screenshots below.)

Is this possible?

On a secondary question, it would be really nice if we could limit Update privileges to specific fields, but that may be too much of an ask. But if anyone knows whether this is possible, I’d like to know that too.

Thanks!

Re: In Esri Enterprise Geodatabase (SQL), is it possible to give Update privileges but not Insert or Delete?

Eugene_Adkins — Thu, 12 Dec 2024 18:02:02 GMT

When you publish a feature service you should have the ability to control whether the feature allows new features to be added or deleted or updated from the configuration tab (screenshot below is Pro 3.1.1). Maybe you're using a new version?

By choosing "attributes only" you can prevent the feature from being moved while still allowing fields to be edited.

To restrict the fields that can be edited there are a few options.

When you publish your feature, you can control whether or not the fields are "read only" in the aprx itself with the data design/fields settings. Be mindful if you choose this option for the fields, they will not have the ability to be edited unless you republish the service with this setting turned off.
If you use Map Viewer classic, you can set whether or not the specified field can be edited by using the configure pop-up/configure attributes/remove the edit capability option (if the published service is being used in the field).
If you use "new" Map Viewer, you can set whether or not the specified field can edited by using the Fields Maps app/content/the "targeted" layer/remove the edit capability option in the smart form itself (if the published service is being used in the field).

There are also some edit settings that can be updated on the server manager side. This might be where you can remove the option(s) for the Feature Access to create or delete while also keeping the option to update without allow geometry updates (i.e. the features can't be moved, only attribute information can be updated):

Hope that helps.

Re: In Esri Enterprise Geodatabase (SQL), is it possible to give Update privileges but not Insert or Delete?

DanielWebb — Thu, 12 Dec 2024 19:12:54 GMT

Just want to clarify your solution. You're thought is that instead of editing the layer directly in the SQL database, I would create an editable service that looks at the layer in the SQL database and edit through that.

Re: In Esri Enterprise Geodatabase (SQL), is it possible to give Update privileges but not Insert or Delete?

Eugene_Adkins — Thu, 12 Dec 2024 19:18:59 GMT

Yes, should've clarified that from the start. Apologies. I thought of it partly through the thought process (with the "in the field" comment) but failed to return to the beginning of the comment to clarify. It's an idea if you have the ability. It's a workflow we have implemented.

Re: In Esri Enterprise Geodatabase (SQL), is it possible to give Update privileges but not Insert or Delete?

DanielWebb — Thu, 12 Dec 2024 19:37:28 GMT

Thanks! Looking at your screenshots and comments, this might actually be what we need. I'll talk to my boss about it and maybe give it a go.

Re: In Esri Enterprise Geodatabase (SQL), is it possible to give Update privileges but not Insert or Delete?

Eugene_Adkins — Thu, 12 Dec 2024 19:52:36 GMT

I think once you get it going it will be the easiest/cleanest solution to limit access from certain accessibilities but still giving the person the ability to do the necessary data updates with worrying about the aprx being used or worrying about any "customization" on the raw data.