Add batch edit widget to experience builder

[MollyJackson]

Experience Builder has so much potential, but we can't implement it until a batch editor capability is added. It is so convenient to be able to select multiple features and edit their attributes simultaneously rather than selecting one-by-one.

[Scott_Sambell]

FYI - There is an AGOL update scheduled for "February" (so sometime in the next 10 days??) and I've been playing around in the early adopter environment for it.

Still no sign of Batch Edit Widget for Experience Builder, but it is present and working for WebEditor.  The only caveat is that it is currently limited to 20 features at a time (or 200 features if you do not have a smart form configured, but we don't have any scenarios where that would be an option)

There is nothing in the release notes for Batch Editor for Experience Build so i assume it will still be quite some time before we see it.

[GrantHoward1]

@Scott_Sambell 

February 2025 update notes released: https://www.esri.com/arcgis-blog/products/arcgis-online/announcements/whats-new-arcgis-online-februa...

yep, just like you mentioned, bulk editing for WebEditor. But not for Experience Builder.

hopefully, it's now an easy jump from WebEditor to EB for the developers! 🤞

[OuterSpatial]

It's becoming difficult to stay patient for this update. Every time there is a new release I run like a child to the "Whats new" release notes seeing if batch editor has been added to ExB. I was let down yet again with this February's release.

ExB shouldn't have been initially released as a replacment for WAB without batch editing. It's too critical.

I guess I'll limp along a bit longer...

[Miralem_Zeljo]

You are not alone Outer Spatial. That is the only thing I was looking for. Glad to see that we have ability to turn all layers on and off but batch edit is much more needed functionality. Hope it is coming soon.

[ChrisH2]

If I could give this 100 kudo's I would.

Having being at the precipice of implementing this in WAB for our users, we held off given that the only other WAB client on our organisation was a generic read-only viewer. At the time, deferring the change management until ExB was ready made sense.

We have a small percentage of users working in Pro, but these are a minority and the opportunities for non-spatially proficient users making errors in editing hosted feature services keep me awake at night.

The combination of bulk edit functionality, smart forms with contingent values and snapping puts simple editing in a managed environment in front of a lot of our users who would otherwise have to make the step to learn Pro.

For us, this functionality outsources simple editing to project coordinators, planners and field supervisors who'll probably never need to learn the intricacies of desktop GIS and is keenly anticipated

[Miralem_Zeljo]

Is it just me or "Early 2025" feels like ages ago?

[MikeDahm]

So they implemented Batch editing in ArcGIS Web Editor for both attribute and deleting/merging.  There appears to be no controls over what fields users can utilize batch attribute as well.  It appears if users have access to a webmap and editable they can open it in ArcGIS Web Editor and have full access to all editable fields to batch attribute edit as well as if add/delete is turned on they can batch delete points as well.  

This is pretty much the opposite of what we need.  Now we don't have control over what attributes people can batch edit and makes it far more likely someone can batch edit in fields they should not be.

Correct me if I am wrong (I am admin so maybe I am not seeing the restriction) but I don't see limits if a webmap is setup and shared with users that include editable layers that are supposed to be used in a web app.   If users figure out they can open the web map in Web Editor they have full multi-edit capability with no restrictions besides if Add/Delete is turned off.  It appears they have rights to edit all fields.

The whole point of the widget was to limit what users could batch attribute.  This tool in Web Editor is opening up a lot of power to many non traditional GIS users.  Most of our apps are meant for limited GIS capable users and don't want unlimited access to tools that can batch edit every attribute.

[GrantHoward1]

reply to @MikeDahm - yikes, that is not ideal. We have a similar setup here where we limit which fields are editable for users. Full editing on all fields could easily result in mass data loss or mass data inaccuracies. 😬

This mess has also caused us to not migrate to the new Map Viewer, because we've noticed several instances where if the "feeder" webmap for a WAB app is built/saved with the new Map Viewer the symbology (and some other features) don't translate properly into the WAB app. So now we have several webmaps that we are forced to use the Classic webmap platform. It's not easy trying to track which maps are Classic and which are new Map Viewer and it's annoying not being able to use just one single platform.

And it's now April 2025!! 😩

What's the latest status update @AlixVezina ?

[AlixVezina]

Hi all, work is being done to get batch editing into Experience Builder in June 2025. The functionality would show up in the existing Edit widget.

[AlixVezina]

@MikeDahm 

There appears to be no controls over what fields users can utilize batch attribute as well.

To control which fields can be edited when batch editing features in Web Editor, you'll need to configure Forms for the layer in Map Viewer. 

See: Configure forms for attribute editing (Map Viewer)—ArcGIS Online Help | Documentation

Also see: Edit attributes—ArcGIS Web Editor | Documentation