Disable ability to capture a photo on parent layer and only allow on related table?

[ctalleygreenville]

I have a hydrant layer with attachments that is related (1-M) table of hydrant inspections. Inspections also have attachments. For the most part, everything is working well in Field Maps. We are utilizing a feature layer view for editing.

Question: Without disabling the attachments altogether on the hydrants, is there a way in Field Maps or on the feature layer view to NOT display the "take a photo" option on the hydrant layer only if it has to be edited or a new one added?  We want to keep the "take a photo" option on the inspection layer.

We want to test the process to only allow a photo on the inspection. It would be easiest to somehow not display the "Take a photo" on the parent hydrant layer, but I have not found a way.

Thanks,

[ChristopherCounsell · Accepted solution]

No...

You can:

• Turn off (hide) attachments on the sublayer in the view. View Item Details > click sublayer > toggle 'show attachments'
• https://doc.arcgis.com/en/arcgis-online/manage-data/manage-hosted-feature-layers.htm#ESRI_SECTION1_3...
• Disable editing on the sublayer using the overly complicated layer overrides rest definition update, but that would require all editing to be disabled and I think give you headaches 
• Consider integration with Survey123 where you can control this at a form level.

Having the update editing capability allows users to add or delete photos on the layer. So any scenario where you allow edits makes it tricky in Field Maps. The most secure way to do this is launch survey123 for inspections and do adds only, a one way feed launched from the asset.

There appears to be some finer controls in Forms coming, such as making photo capture required, and I'd hope that this also includes turning attachments off.

[ctalleygreenville]

Ha, so easy and I couldn't see it.  Your first option:

• Turn off (hide) attachments on the sublayer in the view. View Item Details > click sublayer > toggle 'show attachments'

was exactly what I needed in this scenario. 

Thank you!