1. Editing: why can't we grant different granular permission for each sublayer? For example let's say we have a service with Hydrant points and a related table. We want users to be able to Create, Update and Delete records in the related table. BUT we do NOT want users to able to DELETE hydrant points. It's all or none. Editing permissions on a REST service are identical for all sublayers in a service. We want the points and related table in the service so we can grab the GUID and pass as a foreign key to the related table to maintain the relate, among other things. While there are arcane ways of doing that perhaps with spatially aware arcade or python etc... I can think of a lot of reasons why Orgs would want to have different editing Permissions for each sublayer. Maybe there's a roads layer we only want Create on, but we want create/update/delete on address points, or something; in a Service.
2. Second -- what if we want only SOME fields in a sublayer to be editable? Or perhaps allow create/update on some fields, and create/update/delete on others, or just Create for example.
Thoughts, Enterprise Team?
