Control edit multiple at the field level of a form

[JustinReynolds]

The edit multiple setting is awesome, powerful, and very dangerous.  We want to enable this for our users, but we can't bring ourselves to do it.  It is just too easy, even for seasoned veterans, to overwrite a lot of data.  

It would be nice if we could allow edit multiple on a layer but restrict which fields are allowed to be edited.  In the field maps form authoring a check box just below the existing Allow Editing checkbox seems to be an appropriate location.  This would allow us to provide some level of edit multiple on the fields that often share common data, but restrict edit multiple on fields where that is not appropriate.

I know there is an enhancement request that would utilize the form during edit multiple.  I'm hoping something like this wouldn't need to piggy back of that enhancement but could optionally be implemented ahead of it.

[MeleKoneya1]

Looks like there is no progress on this yet (?)     I have a work flow in Web AppBuilder that cannot be reproduced in Experience Builder due to the lack of batch editor and field maps is prohibitive due to the edit multiple option showing all attributes.      I am not wanting to edit the custom Web AppBuilder  I made many years ago.     None of the Esri field maps truly meet the needs.   Very frustrating

[RobertAnderson3]

This desperately needs to be updated. The fact it exposes all the fields to the editors is an insane oversight data integrity wise.

[MikeDahm]

How is this still not a thing yet?  This should have been released immediately after Field Maps Designer and the forms.  Using ESRI Field Maps is significantly slower and hindered by not allowing forms to be used in edit multiple.  Going to need to look for different software if they won't implement this.  Exposing all of the fields in alphabetical order is absolutely unacceptable and ESRI having it on by default is even worse.

[IngridHogle]

This would help us so much with our field workflows, allowing staff to efficiently update multiple invasive plant patches as treated or not without exposing all of the other, patch-specific fields for update. We often have one mapper assigned to 2-3 people with backpack sprayers. Updating each individual feature is a lot of taps and our staff fall behind what could be accomplished in a day's work if they could safely update just a few relevant fields for multiple features simultaneously.

[LindsayRaabe_FPCWA]

Just reaffirming that this needs to be implemented for the Edit Multiple to be considered a viable option in many of our maps. We have forms setup to restrict and streamline the data capture process. Having multiple fields exposed to editing that are usually not editable is not really an acceptable setting. It's actually less acceptable than if it was single-feature editing as more damage can be done faster!

In addition to your request to enable or disable the use of "Edit Multiple" per field in the form settings, it needs to allow for the auto calculation of fields using Arcade and not just expose the Free Text option. 

[MarkEastwood]

I completely agree with the comments above. I'm surprised to see that this issue was submitted two years ago and there has been no action taken, as it poses serious data integrity problems.

[PaulGeorges]

Hello all,

Any movement on this ?

As per the other comments, this is a critical functionality for me and I simply cannot use FieldMap due to the Edit Multiple poping all fields to everyone.

Frustrating.

[BrendonJoyce1]

Seconded, been waiting years for this.