Latest Contributions by CraigGillgrass

hello @PeterOndruš thanks for raising this issue.  We're aware of this issue and plan to address it for the Fall release of the Web Editor. ... View more

This and the requests in comments have been implemented in Web Editor and are being included in the Editor widget or in Experience Builder.   ... View more

Yes, this was added as part of the June release of Web Editor in ArcGIS Online.  Unfortunately, it did not make the Enterprise 11.5 release. It will be available in the Enterprise 12.0 release. ... View more

@PierreloupDucroix we've addressed this issue in subsequent releases of ArcGIS Enterprise. The issue has not been backported to 11.3.  We are discussing a potential patch for Enterprise 11.3 that could include this fix but no timeline on the patch has been set. ... View more

@ChristopherCounsell is correct @Shawnzeecatz batch attribute editing is only available in Web Editor as of Enterprise 11.5 (and the Spring 2025 release of ArcGIS Online) ... View more

@JosephHilliard94 I did want to mention that you do have some options available to you with the current software: Ownership based access control. This is under the "What features can editors edit?" section of the feature layer settings. While it won't prevent users from deleting their own data, you do mention you'd like users to be able to delete mistakes, but it would prevent them deleting the data of others. Disabling delete on the layer (or on a View you create from the layer). You can then implement a workflow for users who need to delete data by providing them a way to indicate a feature needs to be deleted. One way I've seen this done is using a field that allows users to indicate a feature should be deleted. You, or other users with the applicable privileges, would then delete those features. Or, you could set up a job or a python script that does this. I know this will require work on your side, however, you might want to consider a solution like this.  Even if we add this work to the roadmap, based on the other work we already have scoped out, I don't see it making the next few releases. Again, I apologize if my previous comments were interpreted as being dismissive, we do listen to these requests and, when we determine it's work to pick up, try to get them into a release as soon as possible. Craig ... View more

@KatieQuantrell this is on the roadmap for batch editing, but could not make this release.  We don't have a release assigned yet to do this work, but it is in the plan. ... View more

@PierreloupDucroix no, we are not able to reproduce this issue. If you've already tried the other steps recommended in the thread, I'd suggest contacting Support so they can troubleshoot this with you. ... View more

Hi @JosephHilliard94 I apologize if my replies have come across the wrong way, we are interested in your feedback on this and resolving it. I don't work on the Data tab (I work on the Web Editor which is why I engaged in this post originally).  I have asked the team if they've heard of this request. They have not. This request does cut across multiple teams however, so if its something we're going to address, it will be across multiple areas. Raising this through MyEsri will give you a ticket to follow and allow others to be associated to it. Craig ... View more

it just seems strange to offer two new entry points for mass editing data but not having the same controls. The change doesn't need to be at the feature layer level as we still want the delete option,it's just vital all entry points to a dataset have the same controls to ensure data integrity and the same user experience. For what you've asked for @JosephHilliard94 , it would need to be at the feature layer level.  The Data tab works on feature layers, not web maps.   The different apps teams work together to stay coordinated but sometimes functionality can move at different paces in the different apps. Honestly, this request to block bulk deletions is not one I've heard come in. Maybe other teams have heard this request, I'll check with them. Appreciate your feedback.   ... View more

Hi @BrianHartz_Lumos thanks for trying out the new Web Editor template.  This is a known issue but one you should be able to workaround by configuring the layer search on the web map item details page. You can see the list of Known Issues on our Early Adopter site: https://earlyadopter.esri.com/webeditor ... View more

@JosephHilliard94 thanks for the feedback and clarifying what you're looking for. This is an interesting request and not an easy one to solve. All 3 of the examples you give prompt the user prior to performing the delete to confirm they want to take this action.  Do you still feel users will ignore that prompt and proceed with the delete? You're correct that Experience Builder and Field Maps provide a way to disable bulk editing, but those are both application level specific controls.  We can't take the same approach with Map Viewer and Web Editor; so any approach we'd take would be to provide this per web map, on the Settings tab of the web map's Item Details page. You mention the Data tab under the Feature Layer's Settings tab.  This would not honor a setting on the web map so there would need to be another way to prevent bulk delete.  I don't work on that area of the software and I haven't spoken to the team who does concerning this, however, I believe any approach to solving this would entail a new setting on each feature layer, which as you mentioned above, is not something you're interested in. I'll bring this request up with the larger editing group for discussion.  But due to the complexity of this, I can't provide a ETA for when we'd have a proposal. In the meantime, since all of these examples prompt the user, interested to know if a mix of user education and that prompt will avoid this. ... View more

Hi @JosephHilliard94 is the main concern with bulk delete?  Would like to understand how disabling bulk delete but still allowing the deletion of individual features is a showstopper.  It seems like if the concern is with the deletion of data, you would want to disable that at the feature layer/service level. Just trying to understand what level of controls you and others are looking for so we can provide a solution that means less administration for you.  thanks. ... View more