nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

EB Edit Widget - Geometry Update setting disabled yet allowing geometry edits

kmsmikrud

Hello,

We have an EB app with a couple of edit widgets between two web maps. For editing, we want users to be able to add, delete, update only the attributes of a few layers NOT the geometry. I have the settings for one of these layers as shown below. However, in the app when I click on a polygon it has the pop-up for the polygon but also the polygon is selected (second screenshot) below allowing the polygon to be moved, resized...etc.? We need it enabled for editing but only to allow related table records to be added. How do we disable geometry edits while still allowing new related records? When I turn off editing altogether for the polygon layer we lose the ability to add related records. Are we missing a setting?

EB_EditWidget_WhyIsPolygonGeometryAllowing Geometry Edits.jpg

Thanks in advance!

Kathy

Find more posts tagged with

ArcGIS Online

Accepted answers

All comments

j_patterson

Do we know if this has been resolved or if there's been any communication from Esri on a timeline for fixing this bug? I was just having this issue recently and I am not a fan of having attribute editing restricted to a table if I don't want the geometry edited. Would definitely love to be able to click on a point, have the popup edited and NOT be able to move so said point.

ConorFlynn

FYI, after more testing, it seems our issue was with user permissions. In AGOL, owners and some user types can edit layers even with editing turned off. Apparently the ExB Edit widget follows those rules. Users without those privileges are not able to edit geometry when it is turned off.

Also note that for feature layers with sublayers, you have to turn off geometry editing on each sublayer...!

ConorFlynn

Also, we tried adding custom view layers that had Editing Capabilities restricted to only allow Attribute Only editing, but then the ExB Edit widget doesn't recognize them as editable, it says "The layer is in a read-only state." 😞

ConorFlynn

Thank you for posting this, we are also having this issue. For us, this means that the Edit widget is too dangerous to add to production Experiences.

I wish they'd notify us when this is fixed, but apparently you have to download more Esri software to sign up for notifications....

https://support.esri.com/en-us/bug/unable-to-customize-or-change-the-layer-configuration-f-bug-000173986

MJhendo

Having this issue too! It's very frustrating as there seems to be no way to enable related table editing without simultaneously having geometry editing available in the edit widget - even with geometry editing turned off in the hosted feature layer settings. Don't have views enabled, so the bug mentioned above goes beyond issues with views. Related record editing is only possible using "Interact with a Map widget" with related records turned on, instead of just using attribute only editing - perhaps this behavior is something else ESRI needs to look into further.

kmsmikrud

Hello @makitahideki ,

The conclusion of the tech support case was the following Bug Number: BUG-000173986

Synopsis: Unable to customize or change the layer configuration for the edit widget within views of ArcGIS Online Experience Builder once the application is published.
Status: In Review

Tech support was able to replicate on their side.

What I did learn for the one of the web maps is I did not have the form in the source web map completely configured for the related records as far as adding a related record. In this case the edit widget was honoring the web map form settings even though in EB it wouldn't allow us to view the layers to configure edit settings in the second web map with an edit widget.

As far as the geometry allowing edits despite being disabled as I understand it is a user permissions/level feature so if you are an admin or own the data by default you can change geometry. However a creator/member of a group should in theory not be able to edit geometry.

I'm not sure that answers your question or helps but that is the latest info I had.

Thanks,

Kathy

makitahideki

We are facing exactly the same issue here, do you find any solution for this?

Thanks!

kmsmikrud

Update:

We are still having the issue of the polygon layer despite in the edit widget layer configuration having none of the options selected for 'Add records, delete records, update records' so in theory for this polygon layer nothing should be able to be edited. However the polygons still select on the map and a user can move them/change the geometry. We have tested this with different users including a non administrator or data owner and they can still change the polygon.

We simply want to select a polygon and have the ability to add a related record. If I remove the polygon from the edit widget layers then the ability to add a related record is lost.

I will file a tech support case on this, but I'm not seeing a setting and I thought the user as an administrator/data owner was it, but apparently not the full culprit.

Thanks,

Kathy

abureaux

a bit of a pain

That's putting it lightly 😅

This would be my guess as well. I think I have an Idea somewhere since this behaviour persists into prod last I checked. "No" should mean "no" IMO.

Faiez

Ex.

You can configurate it as you needed.

Best,

Faiez

kmsmikrud

Thanks for the insight and I hadn't thought of it showing differently depending on the user logged in. I am one of the administrators but not the data owner and the app isn't a public app so I'm not even sure actually how to fully test then. One of the users is the data owner, but we will have one of the other AGOL users test and see what they see. Although the data owner also doesn't want to accidentally modify the geometry either so I hope that isn't the case.

I'll update once they test. Thanks for the response!

ChristopherCounsell

Are you testing as a non-owner, non-administrator?

In map viewer and most apps you'll often have greater editing privileges than others if you are the feature layer owner or have admin privileges to edit features owned by other users regardless of settings. It's a bit of a pain during the design and testing process.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.