Latest Contributions by CraigGillgrass

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

It should be in next release of Enterprise, i.e. the release after Enterprise 11.5 @AdmininstratorRDOS  ... View more

@Joshua-Young we're adding the ability to add new records to stand alone tables for the June release of Web Editor.  Take a look for it when that release comes out. ... View more

It will be in either the June or Fall release of Online @AdmininstratorRDOS  ... View more

This is in the plans for an upcoming release. ... View more

Happy to provide the explanation @DerekLutchko_LTC it's going to be a bit of a process for us to find the right UI/UX for this that balances the productivity improvements that batch attribute update bring with the concern with performance and FeatureSet arcade expressions.  This is something we're going to be re-evaluating as we work through it so we can land on the best experience. ... View more

@MikeDahm to clarify; this isn't correct: "Web Editor allows anyone with a Contributor or above user account  ..." Web Editor requires Creator and above. ... View more

@MikeDahm I'd suggest adding this as an idea so others can weigh and vote on it.  We don't have any plans to add this setting as of now; it's just not something we've heard many request for at this time. If we were add it, I don't think we'd disable the toggle by default. That's not how Field Maps settings works and we'd want to stay consistent with Field Maps. ... View more

@DerekLutchko_LTC a few things We're working towards making batch attribute editing available in ExB, this is planned for the June release. The February release is the first release of the functionality and we do plan further updates and improvements.  Specifically, we are working to increase the limits in a future release in the June release. For this first release, we're being conservative when a layer has forms authored, while we continue to optimize the experience.  This is to ensure predictable performance regardless of form complexity.  Batch updating forms that make use of FeatureSet functionality have the potential to degrade performance and the user experience especially if a form contains multiple arcade expressions that use FeatureSets. The 20 feature limit ensures that even when multiple users in an organization are performing batch editing with complex forms they have a consistent and responsive experience. The downside of this is, it impacts forms that don't use the FeatureSet functionality.  That is part of what we're working on for the June release. We appreciate the feedback and know this capability has been something people have been waiting to see for sometime.  We made the decision to include in Web Editor, even with the limits, at this release based on that demand. ... View more

@MohamadChibli there isn't a bug number to track this - you can submit an issue if you require one for tracking ... View more

@MarvinDavis there is not, the Trace tool is in the product plan but no release has been assigned. ... View more

@mwartman_grey this is a known bug that is currently assigned to be fixed in the next release. ... View more