Is there a way to limit which fields users have the ability to batch edit? For both geometry and attribute editing?
Or limit web maps to not be able to be opened in this app? (like Field Maps/Collector selection)
We make lots of maps/apps for our fielders and non traditional GIS users that we don't want to be able to edit any attribute in batch format. We limit them to batch editing through the widgets in Web Appbuilder (Hopefully Experience Builder when widget is released) that allows us to limit which fields they have access to in batch format. From what I can see, if a user has access to the web map and editing geometry add/delete as well as attribute editing is turned on then the user could open the webmap in this Web Editor and have access to batch delete, merge and batch edit all attributes.
At this time, there is no ability to limit or block users from using the batch attribute ability in Web Editor, whether for geometry or attribute updates.
Can you go into a bit of detail of your use case for limiting attributes to edit in the Batch Attribute Editor widget in WAB? What's a scenario where a user can edit the attributes for individual features but not batch features?
There's also no ability to limit the web map from being opened in Web Editor. If the user is a Creator user type then they will have access to Web Editor. Are your fielders and non traditional GIS users Creator user types?
Is ArcGIS Web Editor only available for Creator and above?
Our fielders typically do not have Creator licenses except a few field managers and a few that do some office QA/QC as well as assigning fielders to features. Users sometimes do as we make apps for small Municipal clients and some of them have to be admins on their accounts. We try to get as many people editing as possible by using the restrictions on what they can and can't edit. This get buy in from more municipal users. If they have the ability to batch edit and delete all features in maps they have edit access to it opens up a path to possible large scale data errors from users that aren't traditional GIS users. In the past they would have had to use ArcGIS Pro to do that which they didn't have installed.
Don't get me wrong, it is a great ability to have and glad it is there but I am worried about who has access to it. In the past, the ability for someone to open a web map and edit in there and see attributes they normally would not have write access to was not too much of a problem because they would have to individually edit each feature.
For WAB, we can limit which attributes users can see and edit at all as well as which they have access to for batch attribute. In general we would have several attributes that are read only and users don't have access to editing based on the web map (classic for WAB). For the batch attribute, it is only available through the batch attribute widget. With this widget we can limit which attribute field the users have the ability to batch attribute. That is a major QA feature we use to make sure data editors don't edit multiple features attributes we only want them editing at an individual level.
For instance in a tree editing app we may only give users the ability to batch edit a "year trimmed" field so they could not accidentally change all of the other attributes of a set of trees. All other values we would want them to individually select trees. Using those apps the user also is limited to only be able to edit certain fields.
Or we may create an app for a field manager to assign features to crew members. In that case an app is created that they can batch edit the features but the only attribute field they could batch edit is "Inspector Assigned" and "Status" field.
@MikeDahm Web Editor is only available for Creator and above, correct.
The ability to configure certain fields to not be available for batch editing isn't something that is being considered for the June release, but is something we're discussing. We'll discuss this and see how we can best handle it.
Craig
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
