I wan to edit attributes and related tables of a feature layer, but I don't want my field crew to mess up the geometry of the layer. but here is the dilemma:
If I choose the host feature layer option "update the attributes only", in Collector I can only view the related table records, I can't add.
If I allow "add, delete and update..." on my feature layer, and disable editing for the layer in the web map, the users can't edit the attributes in the feature in the layer, although they can add and edit the records in the related tables
If I allow "add, delete and update..." on my feature layer, and enable editing for the layer in the web map, everything looks good except I can't prevent the users from adding and deleting the features which I really don't wan't them to mess up.
I could manipulate the data and make all the editable contents in the related tables, but I want to symbolize the features using the data collected and using Operational Dashboard, these are not possible with related tables at the moment.
I know we need to be realistic and the desired functions need to compromise with the platform ability. but I want to know if I am alone for this kind of requirement, whether or not it will be good to have more control than only "enable/disable editing" for the feature layer in the webmap?
Any comments are welcome. thanks.