Add batch edit widget to experience builder

10760
41
10-10-2022 10:46 AM
Status: In Product Plan
Labels (1)
MollyJackson
New Contributor III

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.

Tags (1)
41 Comments
HugoAlameda

This is a needed feature. Updating each field one by one is inefficient and Batch Update would streamline and save user a ton of time.

ChaselWood

A decent but still not smooth work around we are using it to create a web app with the batch editor widget and embed it into a separate page in the Experience limiting it to that with some filter options. Our case is probably different in that we are using it to "Dispatch" existing assignments and the rest of the experience pages are dashboards, maps for creating assignments, etc, so it may not be applicable to all cases. 

JakeJacobsAVA

We have multiple web app builder apps with batch edit. Definitely need this to give the users the same experience when we have to convert to Experience Builder.

ConorFlynn

I wonder if the Experience Builder's native editor widget could be configured to allow batch editing multiple selected records?

NourSalamJMT

When will batch attribute editor be added to Experience Builder? This is a high priority widget.

MikeEtterWSB

We require batch attribute editing for Experience Builder too. We have workflows in Web AppBuilder where we are editing hundreds of records at the same time.

AlixVezina
Status changed to: In Product Plan

Batch editing functionality is currently a work in progress and is in the product plan.

Scott_Sambell

This is the only thing stopping us from completely moving all clients over to Experience Builder.  At the moment we have a page on everyone's desktop interface with a WAB with one widget just waiting for this to happen.  

MikeDahm

When will this be implemented?  Way too close to Web AppBuilder retirement not to have some of the basic functionality that was present. 

We can create an app for our projects then turn around in a year and say it is being retired and have to create new apps for them at additional cost when we knew Web AppBuilder would be retired.   We have some multi year projects starting now that we won't be able to change from in the middle but may be forced to use Web AppBuilder because we require batch attribute editing.  

Sietse_de_Haan

We need this sooner than later. Web Appbuilder will be retired soon and we need this function to be there in order to be able to do our work.