read only vs editable features using ArcGIS server layers

[RachelMassa]

I have field maps set up for my field staff with layers referenced from ArcGIS server split into two server layers:

-Read-only layers with no editability

-Editable layers to collect data on

This has been the only way we have found to restrict editing on some of the features in Field Maps. The issue is that there is a relationship between one of the read-only layers and one of the editable layers that is broken when in separate layers. Is there a way to honor the relationship class between the layers while keeping one of the features editable and one read-only? 

[RyanUthoff]

The two feature services are independent from each other, so the behavior you're describing is what I'd expect.

One possible workaround would be to include the editable layer in both the editable and read only feature service. Yes, you would have the same layer twice, but if you really need to access the relationship, you could click the read-only layer (that is also in the editable feature service) and access the relationship that way. It's not the best solution and you'd have two layers representing the same thing in the map, but it may or may not work in your situation.

Besides that, I'm not aware of any solutions that will do what you're wanting unfortunately.

[RachelMassa]

Is there another way to restrict the editability of some features without breaking them into separate feature services?  

[RyanUthoff]

You can disable editing for layers at the map level, but keep in mind that if someone accesses that feature service directly, they'll still be able to edit it.