Why can users submit when field read-only and required?

[DebSF]

I want to restrict users from being able to create new features in a layer they're viewing in Field Maps. I'm not able to create a separate View to control that way, so as a workaround I have made a couple of the fields (using Field Maps Designer):

- Read only

- Required

- Null values not allowed

I thought this would stop the user being able to create and submit a new feature in Field Maps because those fields are blank so shouldn't be able to submit. However this is not the case - users can still submit these features even though the Required fields are blank. Is this a deliberate "feature" in Field Maps? I can't figure out why it's happening.

[KenBuja]

Are you testing this on your own account? If it's on your own account, a quirk in the app is that you have permission to edit anything in what you own, regardless of whether you've set a field to be uneditable. I have set up a testing account with different permissions to check for this.

[DebSF]

I'm using a test account rather than an admin account, so they should be very limited in what they can edit.

[tiztrain]

To address 'read only' did you turn off editing for the view service?

I am also having issues with the 'mandatory' fields. Users can still complete the form even those those fields are not filled out.

I am going to raise a ticket with esri on this one.

[DebSF]

The editing is just turned off at the field level in the form, rather than service level. I can't change it at a service level as other users do need to be able to edit the geometry.